Fastfile Best Practices
summary
Shows how to turn messy Fastfiles into reusable automation: load per-config variables with dot-env files (.env.default, .env.prod, .env.kit), keep only build output and minimal params in lanes, and split lanes into separate Fastfiles. Uses fastlane actions and import_from_git to share automation across apps; team automates ~80 private components this way. Hardcodes long-lived flags like skip_waiting_for_build=true to avoid wasting ~15 minutes per build. Approach is implemented and reduces duplication.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:30Fastfile problems
- 5:25Dotenv solution
- 9:58RickVars validation
- 12:06Fastfile decomposition
- 13:51Reusing Fastfile
- 16:17Private code handling
- 23:04Summary
related talks
46mAutomating with fastlane Tips, Tricks, and Best Practices
21mFastlane: Automate Deployment of Your Mobile Apps to the St…
24mAutomate your React Native world with fastlane
30mScale-up iOS Automated UI Tests
46mAutomatic Deployment of iOS and/or Android Apps
16mMobile CI Server with GitLab CI and Fastlane
40mMy Best Practices for iOS CI with GitHub Actions
10mFastbuild
