In this post, we will take a look at how to integrate fastlane into your iOS app. This guide is for iOS, but the process should be similar on Android as well.

We will go through the complete setup, and I will give you insights into some of the best practices when using fastlane.

This is the second post in the series, so if you are not sure yet whether fastlane is for you, check out the first post. Now start your terminals and get ready!


To get started with fastlane, you need to install it first. There are multiple ways to do this which you can find in the documentation here.
To start things off you need to have Xcode installed, which is easy enough from the terminal:

xcode-select --install

Next, install fastlane using homebrew:

brew cask install fastlane

This is my preferred installation method. It has the advantage of coming with a complete, self-contained ruby installation and all required dependencies baked in.

This way is most likely to work right out of the box, but there are some cases where other installation methods might be a better option. You can check out the docs link above if homebrew doesn’t work for you.

There is one thing left to do before you can start using fastlane regardless of installation method, which is to configure your locale settings correctly. fastlane needs a UTF-8 locale or some of the tools won’t work. In some cases you might only get warnings, in others builds might fail or hang until you cancel them.

Setting the locale is as simple as setting the LANG and LC_ALL variables in your terminal:

export LC_ALL=en_US.UTF-8
export LANG=en_US.UTF-8

If you want to persist these settings, you need to edit your ~/.bashrc, ~/.zshrc or ~/.config/fish/ file and add the lines above. Which file you need to use depends on which shell you are using, ~/.bashrc being the default on macOS. You could also run this simple script which will add the required lines to the correct files:

bash -c 'echo -e ".bashrc\n.zshrc\n.config/fish/" | while read f; do if [ -f $HOME/$f ]; then echo -e "export LC_ALL=en_US.UTF-8\nexport LANG=en_US.UTF-8" >> $HOME/$f; fi; done'

After this, restart your terminal and you are ready to start using fastlane.

Getting Started

As we saw in my last post, fastlane is mostly controlled through a configuration file (the Fastfile) located in the fastlane/ subfolder in your project directory. You can create this folder and the Fastfile manually if you want, but for the purpose of this guide we will let fastlane do the work for us.

In your project directory run:

fastlane init

fastlane will proceed to ask you some questions about your project including your Apple ID and password. Note that fastlane uses the terms “bundle ID” and “app ID” interchangeably.

As soon as you confirm your app’s bundle ID, a couple things will happen:

Note that fastlane will always save your credentials in your system’s keychain after you’ve entered them for the first time. If you do not want that, you can also set your username and password by setting the FASTLANE_USER and FASTLANE_PASSWORD environment variables.

Let’s take a look at everything that fastlane has created for us:

fastlane directory, with Appfile, Deliverfile, Fastfile and metadata and screenshots folders

We can see that there is the Fastfile that we’ve talked about, but also an Appfile and Deliverfile.
The Appfile is a special kind of configuration file that is used by all the tools included in fastlane. It contains general project information like the Apple ID you entered for this project, the bundle ID, and your team’s ID.
You can ignore the Deliverfile since you are using fastlane.

The metadata and screenshots folders contain everything that deliver managed to download from iTunes Connect. All the files in the metadata folder are simple text files, and everything you hadn’t filled out yet will be created for you. This allows you to check all your metadata into your SCM and treat it just like source code. How neat is that?

fastlane creates some temporary files which you probably don’t want to go into your repository.
Before we go on, it’s helpful to add the following lines to your .gitignore file in your project directory:

# fastlane specific

# deliver temporary files

# snapshot generated screenshots

# scan temporary files

Configuring fastlane

If we take a look at the generated Fastfile we can see that it already includes some lanes and some other configuration.

Something that we haven’t discussed yet when I was talking about the DSL is the platform block, which simply scopes all the lanes it contains to a single platform.
For a multi-platform project this allows you to have a single Fastfile to support all the platforms your project supports. If you are using different platforms you would call the lanes from your command line with fastlane <platform> <lane>.

If your project only has a single platform, you can remove the lines with platform from your Fastfile and place all your lanes at the top level of the file.

Right off the bat, I would suggest you uncomment the line update_fastlane at the beginning. It will ensure that your fastlane installation is always up to date every time you run it. This is important because fastlane depends on Apple’s webservers - which tend to have breaking API changes frequently and unexpectedly.

Setting up the Xcode project for fastlane

To actually compile your project, fastlane will need access to your project’s schemes. Check that you are sharing your schemes by opening Xcode, and clicking on Product > Scheme > Manage Schemes... in your menu bar.
Make sure the Autocreate schemes and Shared boxes are ticked:

Xcode Scheme Editor, with 'Autocreate Schemes' and 'Shared' enabled for the project

Next, we want to set up fastlane to be able to manipulate version information.
This is a straightforward process:

Making it useful

Now we can explore the pre-existing lanes. If you run fastlane lanes you will get a list of all of them.

The beta and release lanes will most likely not work right away, but you can try running the test lane. As a reward, you will get some nice output that should be showing you if all your tests have passed.


To get automatic screenshot creation you need to use Xcode UI tests. If you aren’t using them already, you can simply add them by clicking on your project file in Xcode and clicking on Editor > New Target... in the menu bar. Scroll down until you find iOS UI Testing Bundle and add it to your project.
Then, we can let fastlane set everything up for us:

fastlane snapshot init

This will create two new files in your fastlane directory - the Snapfile and SnapshotHelper.swift. Everything you need to know about the Snapfile is explained inside, so take a look at it. You should set all the languages that you want screenshots for as well as the list of devices by uncommenting the respective lines.
Now go back to Xcode and add the SnapshotHelper to your UI test target:

let app = XCUIApplication()

Now you are ready to have snapshot take your screenshots for you.

Integrating with UI tests

The easiest way to do this is to open your UI tests, create a new function testTakeScreenshots, and then use Xcode’s record function to navigate to the screens you want to take screenshots of.
Then you simply insert the line snapshot(<filename>) for each screenshot you want to take:

func testTakeScreenshots() {
  // Navigation...
  // Navigation...
  // ...

Make sure to name the screenshots accordingly, because they will be uploaded alphabetically. The easiest way to do this is just to prepend a number to the filename like you see above.

Once you are done with everything, uncomment snapshot inside of your release lane. You should also be able to run fastlane snapshot directly at this point and all your screenshots will be created for you.

snapshot usually also creates a nice HTML preview site, which it automatically opens for you. You can stop it from doing that by using the skip_open_summary parameter:

  skip_open_summary: true

Note: If you are missing some simulators, you can have fastlane recreate the “standard” list of simulators by running fastlane snapshot reset_simulators. This will delete all your old simulators and create new ones.

Completing the configuration

After you’re done with the previous steps, make sure to commit your changes to your version control system.
At this point you can also add a before_all block at the start of your Fastfile to make sure no one deploys a new version with uncommitted changes:

before_all do

Both TestFlight and the App Store require you to submit builds with differing build numbers, so it is a good idea to have fastlane do it for you.
Don’t worry, it’s really simple:

lane :build do
  # Add +1 to the build number

  # Build your app

  # The version bump causes your project file to be modified, so it has to be committed and pushed to your remote

Then, simply replace the gym line in your beta and release lanes with your newly created build lane.

Wrapping up

To make this setup work for you, you will probably need to add some parameters to some of the actions: for example, if you have multiple schemes or targets in your app, actions like scan or gym will require you to set those. You can find out which parameters an action supports by running fastlane action <action_name>.

Finally, our last remaining issue: we haven’t yet set up match to handle code signing for us. We will explore how match works and the approach match uses to sync all our code signing data in the next post.