checkout my repo<\/a> before you start, feel free!<\/p>\n\n\n\nGetting in motion<\/h2>\n\n\n\n
When using Fastlanes you should really remember if you\u2019re going to pass parameters from the command line to your lane, use the following syntax:<\/p>\n\n\n\n
fastlane [lane] key:value key2:value2\nfastlane deploy submit:false build_number:24<\/code><\/pre>\n\n\n\nPassing values between lanes<\/h2>\n\n\n\n
In theory, you can have as many lanes<\/code> as you want, so you can invoke variant lanes<\/code>. Example being:<\/p>\n\n\n\nbefore_each do |lane, options|\n # lane number (Montana likes # 3) \nend<\/code><\/pre>\n\n\n\nNow within lanes, you can INVOKE<\/em> other lanes for various other reasons, in other words, each lane can have different functions essentially:<\/p>\n\n\n\nerror do |lane, exception, options|\n if options[:debug]\n puts \"This is a cool lane because you're in it with Montana\"\n end\nend<\/code><\/pre>\n\n\n\nSwitching lanes<\/h2>\n\n\n\n
If you\u2019ve used Fastlane<\/code> at length, you\u2019ll know switching lanes<\/code> is usually called lane hopping<\/code>. You can lane hop feasibly, without using too much CPU:<\/p>\n\n\n\nlane :deploy do |options|\n # lane 3 \n build(release: true) # don't forget this part! - Montana\n Montana Mendy\n # invoking lane 4 with a conditional \nend<\/code><\/pre>\n\n\n\nQuerying lanes<\/h2>\n\n\n\n
Just like anything you query, you can retrieve the return value in this case it\u2019s through a lane callback<\/code>. In Ruby, the last line of the lane definition is the return value. Here is an example:<\/p>\n\n\n\nlane :deploy do |options|\n value = calculate(value: 3)\n puts value # => 5\nend\n\nlane :calculate do |options|\n # ...\n 2 + options[:value] # This is always the return value line. - Montana \nend<\/code><\/pre>\n\n\n\nExecuting lanes early<\/h2>\n\n\n\n
You in theory never want to reach the end of a lane<\/code>, and if you do – you\u2019re not going to be executing much longer:<\/p>\n\n\n\nlane :build do |options|\n if cached_build_available?\n UI.important 'Montana cached this Lane!'\n next # Montana is skipping doing the rest of this lane\n end\n match\n gym\nend\n\nprivate_lane :cached_build_available? do |options|\n # ...\n true\nend<\/code><\/pre>\n\n\n\nSo while executing lanes<\/code> – there are conditionals you can use, such as next<\/code> is used during a lane<\/code> and switch<\/code>, control<\/code> returns to the previous lane that was executing, so lanes<\/code> in theory can revert back and forth.<\/p>\n\n\n\nlane :first_lane do |options|\n puts \"If you run: `fastlane first_lane`\"\n puts \"You'll see this!\"\n second_lane\n puts \"Montana is in this lane!\"\nend\n\nprivate_lane :second_lane do |options|\n next\n puts \"Hidden!\"\nend<\/code><\/pre>\n\n\n\nWhen you stop executing a lane<\/code> early with next (lane switching<\/code>), any after_each<\/code> and after_all<\/code> blocks you have will still trigger as usual :+1:<\/code>. This would include being called (via a lane callback<\/code>) before each lane you\u2019ve switched to.<\/p>\n\n\n\nbefore_each do |lane, options|\n # ...\nend<\/code><\/pre>\n\n\n\nSo this is a good reminder from myself, that when doing after_each<\/code> blocks are called (again, by the lane callback<\/code>) after any lane is called. This would include being called after each lane you\u2019ve switched to. Just like after_all<\/code>, after_each<\/code> is not called if an error occurs. The error block should be used in this case.<\/p>\n\n\n\nFeasibility of lanes<\/h2>\n\n\n\n
With all these scenarios, before_each<\/code> and after_each<\/code> would be called 4 times, by the lane callback<\/code>. Remember before the deploy lane, before the switch to archive, sign, and upload, and after each of these lanes as well, a lot of users forget.<\/p>\n\n\n\nLane context<\/h2>\n\n\n\n
Now Fastlane<\/code> has different actions that can communicate with each other using a shared hash, in other words, communicating with other lanes<\/code>. You can access this in your (lanes, actions, plugins etc.):<\/p>\n\n\n\nlane_context[SharedValues::BUILD_NUMBER] # Generated by `increment_build_number`\nlane_context[SharedValues::VERSION_NUMBER] # Generated by `increment_version_number`\nlane_context[SharedValues::SNAPSHOT_SCREENSHOTS_PATH] # Generated by _snapshot_\nlane_context[SharedValues::PRODUCE_APPLE_ID] # The Apple ID of the newly created app\nlane_context[SharedValues::IPA_OUTPUT_PATH] # Generated by _gym_\nlane_context[SharedValues::DSYM_OUTPUT_PATH] # Generated by _gym_\nlane_context[SharedValues::SIGH_PROFILE_PATH] # Generated by _sigh_\nlane_context[SharedValues::SIGH_UDID] # The UDID of the generated provisioning profile\nlane_context[SharedValues::HOCKEY_DOWNLOAD_LINK] # Generated by `hockey`\nlane_context[SharedValues::GRADLE_APK_OUTPUT_PATH] # Generated by `gradle`\nlane_context[SharedValues::GRADLE_ALL_APK_OUTPUT_PATHS] # Generated by `gradle`\nlane_context[SharedValues::GRADLE_FLAVOR] # Generated by `gradle`\nlane_context[SharedValues::GRADLE_BUILD_TYPE] # Generated by `gradle`<\/code><\/pre>\n\n\n\nTo feasibly get information about available lane variables, available lanes to switch on, run fastlane action [action_name]<\/code> or look at the generated table in the action documentation.<\/p>\n\n\n\nLane properties<\/h2>\n\n\n\n
It can be useful to dynamically access some properties of the current lane. These are available in the lane_context<\/code> as well:<\/p>\n\n\n\nlane_context[SharedValues::PLATFORM_NAME] # Platform name, e.g. `:ios`, `:android` or empty (for root level lanes)\nlane_context[SharedValues::LANE_NAME] # The name of the current lane preceded by the platform name (stays the same when switching lanes)\nlane_context[SharedValues::DEFAULT_PLATFORM] # Default platform<\/code><\/pre>\n\n\n\nThey are also available as environment variables:<\/p>\n\n\n\n
ENV[\"FASTLANE_PLATFORM_NAME\"]\nENV[\"FASTLANE_LANE_NAME\"]<\/code><\/pre>\n\n\n\nPrivate lanes<\/h2>\n\n\n\n
Sometimes you might have a lane that is used from different lanes, or a lane from a hopped lane<\/code>:<\/p>\n\n\n\nlane :production do\n # ...\n build(release: true)\n appstore # Deploy to the Montana's brain\n # ...\nend<\/code><\/pre>\n\n\n\n-><\/p>\n\n\n\n
lane :beta do\n # ...\n build(release: false)\n crashlytics # Distribute to testers\n # ...\nend<\/code><\/pre>\n\n\n\n-><\/p>\n\n\n\n
lane :build do |options|\n # ...\n Montana likes beer\n # ...\nend\nIt probably doesn't make sense to execute the build lane directly using fastlane build. You can hide this lane using<\/code><\/pre>\n\n\n\n-><\/p>\n\n\n\n
private_lane :build do |options|\n # ...\nend<\/code><\/pre>\n\n\n\nThis will hide the lane from:<\/p>\n\n\n\n
fastlane lanes\nfastlane list\nfastlane docs<\/code><\/pre>\n\n\n\nAnd also, you can\u2019t call the private lane using fastlane build. The resulting private lane can only be called from another lane using the lane switching technology, or the lane callback<\/code>.<\/p>\n\n\n\nIn general, configuration files take only the first value given for a particular configuration item. That means that for an Appfile like the following:<\/p>\n\n\n\n
app_identifier \"com.used.id\"\napp_identifier \"com.ignored.id\"<\/code><\/pre>\n\n\n\nSo, the app_identfier<\/code> will be \u201ccom.used.id\u201d and the second value will be ignored. The for_lane and for_platform configuration blocks provide a limited exception to this rule.<\/p>\n\n\n\nAll configuration files (Appfile, Matchfile, Screengrabfile, etc.) can use for_lane<\/code> and for_platform blocks<\/code> to control (and override) configuration values for those circumstances.<\/p>\n\n\n\nSo for_lane<\/code> blocks will be called when the name of lane invoked on the command line matches the one specified by the block. So, given a Screengrabfile like:<\/p>\n\n\n\nFor the locales (language lane): locales ['en-US', 'fr-FR', 'ja-JP']<\/code><\/p>\n\n\n\nfor_lane :screenshots_english_only do\n locales ['en-US']\nend<\/code><\/pre>\n\n\n\nfor_lane :screenshots_french_only do\n locales ['fr-FR']\nend<\/code><\/pre>\n\n\n\nSo as you can see, the locales will have the values [\u2018en-US\u2019, \u2018fr-FR\u2019, \u2018ja-JP\u2019] by default, but will only have one value when running the fastlane screenshots_english_only<\/code> or fastlane screenshots_french_only<\/code>.<\/p>\n\n\n\nThen, for_platform<\/code> gives you similar control based on the platform for which you have invoked fastlane. So, for an Appfile configured like:<\/p>\n\n\n\napp_identifier \"com.default.id\"\n\nfor_lane :enterprise do\n app_identifier \"com.forlane.enterprise\"\nend<\/code><\/pre>\n\n\n\nfor_platform :mac do\n app_identifier \"com.forplatform.mac\"\n\n for_lane :release do\n app_identifier \"com.forplatform.mac.forlane.release\"\n end\nend<\/code><\/pre>\n\n\n\nSo now you can expect the app_identifier<\/code> to equal \u201ccom.forplatform.mac.forlane.release\u201d when invoking Fastlane mac release.<\/p>\n\n\n\nIs it plausible to change the fastlane execution folder while inside a lane?<\/h2>\n\n\n\n
Yes, you can do this. The way I\u2019ve classically done this is make two fastlane lanes, one for the old location, one for the new, so then your new script looks somethng like this:<\/p>\n\n\n\n
cd old-location\nfastlane old_lane\ncp -r old-location new-location\ncd new-location\nfastlane new_lane<\/code><\/pre>\n\n\n\nSetting fastlane up in iOS for different export methods and provision profiles?<\/h2>\n\n\n\n
So my guess is that anyway your project is scoped you have more than 1 bundle<\/code> identifier to the different apps in question.<\/p>\n\n\n\nRemember with Fastlane you can setup a new target and just create the same lane with a different scheme for that target (or build a function and send the correct scheme as a parameter). You will also have to create a different bundle id<\/code>.<\/p>\n\n\n\nIf you don\u2019t wish to create a different target and you are you using Automatic signing on your project, (some SSO), you will have to change it to manual and specify the provisioning profile there.<\/p>\n\n\n\n
Please make sure there\u2019s nothing that could conflict with Travis or Fastlane, so it should look like something like this:<\/p>\n\n\n\n
Prod<\/p>\n\n\n\n
build_app(\n workspace: \"XXXX.xcworkspace\",\n scheme: \"XXXXX\",\n ......\n export_options: {\n method: \"app-store\",\n signingStyle: 'manual',\n provisioningProfiles: {\n \"bundle id\": \"Prod profile full name\",\n }\n })<\/code><\/pre>\n\n\n\nAd-hoc<\/p>\n\n\n\n
build_app(\n workspace: \"XXXX.xcworkspace\",\n scheme: \"XXXXX\",\n ......\n export_options: {\n method: \"ad-hoc\",\n signingStyle: 'manual',\n provisioningProfiles: {\n \"bundle id\": \"Montana's project\",\n }\n })<\/code><\/pre>\n\n\n\n