Blog DevOps Mobile DevOps with GitLab, Part 3 - Code signing for iOS with GitLab CI and Fastlane
Published on: October 3, 2022
5 min read

Mobile DevOps with GitLab, Part 3 - Code signing for iOS with GitLab CI and Fastlane

Learn how to use Project-level Secure Files with Fastlane Match to sign an iOS app.


This post is the third in a series of three blog posts showing how GitLab makes code signing easier using a new feature called Project-level Secure Files.

  • Part 1 introduces the Project-level Secure Files feature and the basics of getting started.
  • Part 2 shows an example of how to use Project-level Secure Files to sign an Android app.
  • This post shows how to use the integration with Fastlane Match to sign an iOS app.

Code signing for iOS projects is notoriously difficult and can lead to a lot of time spent debugging errors, but a tool called Fastlane makes it much easier. Fastlane is an open source tool that greatly simplifies the complexity of the code signing process for iOS development.

In Fastlane 2.207.2 we released support for Project-level Secure Files as a storage backend for Fastlane Match, making it even easier for mobile projects to manage their signing certificates and provisioning profiles within GitLab. Now, we will cover a couple of ways to get started using Project-level Secure Files in a Fastlane project.

Set up Fastlane Match

If your project doesn't have a Fastlane Matchfile yet, you can generate one by running the following:

bundle exec fastlane match init

This command will prompt you to choose which storage backend you want to use (select gitlab_secure_files) and to input your project path (for example: gitlab-org/gitlab). It will then generate a Fastlane Matchfile configured to use your project's secure files for Fastlane Match.

Initialize Fastlane Match

Generate a Personal Access Token

Next, you'll need a GitLab Personal Access Token to use Fastlane Match from your local machine. To create a Personal Access Token, visit the Access Tokens section in your GitLab profile (for example: Create a new token with the “api” scope. Take note of the token you just created, we'll be using it later.

Generate and upload

If you have not created signing certificates or provisioning profiles yet for your project, running Fastlane Match will do all of the work for you. Run the command below with your Personal Access Token:

PRIVATE_TOKEN=YOUR-TOKEN bundle exec fastlane match 

You may be prompted to log in with your Apple developer account. Once authenticated, this command will generate development certificates and profiles in the Apple Developer portal and upload those files to GitLab. You'll be able to view the files in your project's CI/CD settings as soon as the command completes.

You can also generate other certificate types by specifying the type in the command, for example:

PRIVATE_TOKEN=YOUR-TOKEN bundle exec fastlane match appstore


If you have already created signing certificates and provisioning profiles for your project, you can use Fastlane Match Import to load your existing files into Project-level Secure Files. Simply run:

PRIVATE_TOKEN=YOUR-TOKEN bundle exec fastlane match import

You'll be prompted to input the path to your files. Once those options are provided, your files will be uploaded and visible in your project's CI/CD settings. (Note: If you are prompted for the git_url during the import, it is safe to leave it blank and hit enter.)

Fastlane Match Import

CI/CD pipelines

With your signing certificates and provisioning profiles loaded in Project-level Secure Files, it's now easy to use those files in your CI/CD pipelines. No access tokens are needed when running jobs in GitLab, so you can load your files into a CI/CD job by adding the fastlane command to a CI job script. For example:

  stage: test
    bundle exec fastlane match –readonly

Using the –readonly flag on CI is suggested to prevent any unintended changes to signing certificates by Fastlane. The Fastlane Match command will sync the certificates to the machine, but does not build the application. To run match and build, configure a lane in your project's Fastfile to do both steps. For example:



platform :ios do
  desc "Build the App"
  lane :build do
    match(type: 'appstore', readonly: is_ci)
      clean: true,
      project: "ios_demo.xcodeproj", 
      scheme: "ios_demo"



.gitlab-ci.yml File

  stage: build
    - bundle exec fastlane build

With all of that in place, you'll have a CI pipeline that runs a single build job. That job will use the :build lane from fastlane to run setup_ci, match, and build_app. The result from that job will be a build of your app, signed with the certificates stored in your project with Project-level Secure Files. You could then extend fastlane to push that build to Test Flight or the App Store.

Fastlane does a good job of handling the complexity associated with certificate management, so you don't have to worry about it, but there is a bit of a learning curve to getting used to Fastlane. Take a look at this branch in the ios_demo project to for a full working example. Please add any feedback you have in the feedback issue.

Better Mobile DevOps

With Project-level Secure Files, you no longer need to rely on hacks or workarounds to automate code signing, and it can be easily added to new or existing CI/CD pipelines.

For more about how we are working to make better Mobile DevOps at GitLab, check out the Mobile DevOps Docs, SaaS runners on macOS, and the Mobile DevOps Playlist on GitLab Unfiltered.

Cover image by Vinicius "amnx" Amano on Unsplash

We want to hear from you

Enjoyed reading this blog post or have questions or feedback? Share your thoughts by creating a new topic in the GitLab community forum. Share your feedback

Ready to get started?

See what your team could do with a unified DevSecOps Platform.

Get free trial

New to GitLab and not sure where to start?

Get started guide

Learn about what GitLab can do for your team

Talk to an expert