Mobile Fastlane

Interactive setup overview

Last updated 2026-10-07

The interactive setup turns the framework into a guided CLI. You don't need to memorise lane options such as environment:staging gradle_flags:… or edit YAML before every build. Answer a few questions, and the framework builds the right variant and remembers your answers for next time.

CommandWhen you use itInteractive?
bundle exec fastlane init_projectOnce per project. Generates fastlane/config/environments.yml.Yes
bundle exec fastlane setupEvery local build. Reuse a previous setup or create a new one.Yes
bundle exec fastlane run_profile name:<profile>CI, scripts, or when you already know the profile.No
bundle exec fastlane profilesList saved profiles and the last one used.No

What the wizard asks

Use last / saved setup, or create a new one
Platform: Android, iOS or both
Environment: development, staging, uat, production or your own
Android: flavor → build type → APK or AAB → Gradle task & output path
iOS: scheme → export method
Action: build only, or build + distribute (Firebase / TestFlight)
Testers, AI testing, release notes
Summary → confirm → save as profile → doctor → build / distribute

How it fits with the existing lanes

The wizard does not replace the platform lanes. It produces a profile: a small YAML file that uses the same keys as an environment block in environments.yml. At run time the profile is deep-merged over that environment, and the normal android doctor / build / distribute (or ios …) lanes run. Validation, production guards and notifications therefore behave exactly as before.

Note: the framework uses the prompt helpers built into fastlane (UI.select, UI.input, UI.confirm), so it adds no extra gems. See fastlane lanes for how platform lanes and options work.

Official documentation

Was this helpful?