iOS Build Automation: Setting Up CI/CD with Fastlane

Setting Up CI/CD for iOS Apps Using Fastlane

We set up CI/CD for you using Fastlane—the de facto standard for iOS build automation outside the Apple ecosystem. Fastlane runs on any CI: GitHub Actions, GitLab CI, Jenkins, Bitrise. Its main advantage over Xcode Cloud is full control over every step and the ability to run the same commands locally that CI executes.

Once we worked on a project where a CI build took 40 minutes due to missing caching and suboptimal code signing configuration. After setting up Fastlane with Match and proper caching, the time dropped to 15 minutes—saving over 60% of the team's time. Automating with Fastlane reduces build time by 40% and saves up to $2000 per month for a team of five developers. Our team, with 5 years of experience and over 40 completed projects, ensures a reliable configuration.

Why Code Signing Is a Headache on CI

iOS requires a valid provisioning profile and certificate for any build that isn't on a simulator. On a local machine, these reside in the Keychain. On a CI server—they don't. Without proper setup, fastlane consistently fails with Code Signing Error: No profiles for bundle ID found.

fastlane match solves this: all certificates and profiles are stored encrypted in a separate Git repository (or S3/Google Cloud). On CI, a single command bundle exec fastlane match adhoc downloads and installs the needed profile. The passphrase for match is a CI secret variable.

The scheme:

Git repository (encrypted) ←→ fastlane match ←→ Apple Developer Portal
                                            ↓
                                    CI Keychain (temporary)

For a team of 5+ developers, match in readonly mode on CI and normal mode on developer machines is the standard configuration. This eliminates collisions during simultaneous work.

How to Configure Fastlane for Building and Deployment

Structure of Fastfile:

default_platform(:ios)

platform :ios do
  before_all do
    setup_ci if ENV['CI']  # Creates a temporary keychain on CI
  end

  lane :test do
    run_tests(
      scheme: "MyApp",
      devices: ["iPhone 15", "iPhone SE (3rd generation)"],
      code_coverage: true
    )
  end

  lane :beta do
    match(type: "adhoc", readonly: true)
    increment_build_number(
      build_number: ENV["CI_PIPELINE_ID"] || Time.now.to_i.to_s
    )
    build_ios_app(
      scheme: "MyApp",
      configuration: "Release",
      export_method: "ad-hoc"
    )
    firebase_app_distribution(
      app: ENV["FIREBASE_APP_ID"],
      groups: "qa-team",
      release_notes: changelog_from_git_commits(commits_count: 5)
    )
  end

  lane :release do
    match(type: "appstore", readonly: true)
    increment_build_number(build_number: latest_testflight_build_number + 1)
    build_ios_app(scheme: "MyApp", configuration: "Release", export_method: "app-store")
    upload_to_testflight(skip_waiting_for_build_processing: true)
    slack(message: "New build uploaded to TestFlight!", channel: "#releases")
  end
end

setup_ci creates a temporary keychain within the CI job. Without it, fastlane tries to open the user keychain, which is unavailable on headless CI.

How to Set Up Fastlane in 5 Steps

1. Install Fastlane and initialize the project: bundle init, then fastlane init.
2. Create an encrypted Git repository for Match and configure access.
3. Describe lanes in Fastfile: at minimum test, beta, release.
4. Configure the CI script (GitHub Actions, GitLab CI, or other) on a macOS runner.
5. Run a test on CI and debug any errors.

Build Number

increment_build_number without arguments reads the current number from Info.plist and increments by 1. But with parallel CI jobs, collisions can occur—two PRs building simultaneously get the same number. Solution: use CI_PIPELINE_ID (GitLab) or github.run_number (GitHub Actions) as the build number. This guarantees uniqueness.

Comparison: Fastlane vs Xcode Cloud

Fastlane is better for projects requiring custom pipelines and integration with external services (Firebase, Slack). Xcode Cloud suits simple projects within the Apple ecosystem.

Integration with GitHub Actions

- name: Run Fastlane Beta
  env:
    MATCH_PASSWORD: ${{ secrets.MATCH_PASSWORD }}
    MATCH_GIT_BASIC_AUTHORIZATION: ${{ secrets.MATCH_GIT_AUTH }}
    FIREBASE_APP_ID: ${{ secrets.FIREBASE_APP_ID }}
    FIREBASE_TOKEN: ${{ secrets.FIREBASE_CLI_TOKEN }}
  run: bundle exec fastlane beta

The runner must be macOS (runs-on: macos-14). Linux runners are not suitable for iOS builds because Xcode only runs on macOS.

Dependency Caching

The longest step is pod install or swift package resolve. On GitHub Actions, we cache:

- name: Cache CocoaPods
  uses: actions/cache@v4
  with:
    path: Pods
    key: ${{ runner.os }}-pods-${{ hashFiles('Podfile.lock') }}

This saves 3–8 minutes per run when Podfile.lock hasn't changed. If using Swift Package Manager, cache .build similarly.

Common Mistakes When Setting Up Fastlane

What's Included in the Work

We provide a full package:

• Fastlane configuration: Fastfile, Matchfile, Appfile
• CI scripts (GitHub Actions / GitLab CI / etc.) with caching
• Match setup: encrypted certificate repository
• Documentation for running and maintaining
• Team training (1 hour online)
• 30-day workability guarantee
• Support for certificate or device changes

Contact us to discuss CI/CD setup for your project. Order Fastlane configuration and get a ready pipeline in 3–5 days.

Timelines

Basic Fastlane setup with match, test, and beta lanes on GitHub Actions: 3–5 days. Full configuration with release lane, changelog, Slack notifications, caching, and multi-scheme support: 1–2 weeks. The price is calculated individually based on project complexity.

— Fastlane — an open source project.

CI/CD for Mobile Apps: Fastlane, Codemagic, Bitrise, and GitHub Actions

Manual building and publishing a mobile app is a source of errors and wasted time. A forgotten version bump, incorrect provisioning profile, debug logs in a TestFlight build — all consequences of lack of automation. A typical team spends 3–4 hours per week on manual build operations. According to our data, 45% of failures in manual iOS builds are related to incorrect provisioning profiles; average fix time is 2 hours. Automation via Fastlane and Match eliminates this problem entirely.

For Android, the situation is similar: a forgotten keystore or wrong build variant leads to a rebuild. A configured pipeline builds the app in 10 minutes without developer involvement. Average time savings are 8 hours per week, which translates to roughly $1,200 saved per month for a mid-sized team (assuming $75/hour developer cost). As a result, the team focuses on features, not the release process. Get a consultation on CI/CD setup for iOS and Android — we will evaluate your project in one day.

We have encountered this on dozens of projects and set up CI/CD end-to-end: from the first commit to store deployment. Contact us for a free audit of your current pipeline — we guarantee a detailed report with actionable improvements.

What problems does CI/CD solve?

• Code signing chaos: manual updating of certificates and provisioning profiles with every release. Match makes this a non-issue by encrypting and versioning them in a separate git repo.
• Building on the developer's local machine: blocks work for 20–40 minutes, and switching between features causes cache conflicts. CI parallelizes builds across environments.
• Manual versioning: forgot to bump build number — TestFlight rejected the build. Rebuilding with the correct number takes another hour. Automation fixes this in seconds.
• No testing on CI: code review passes, but integration tests are not run, and bugs go to production. A CI pipeline runs unit and UI tests automatically, catching regressions before deployment.

How does Fastlane solve code signing?

Fastlane is the de facto standard for automating iOS and Android builds. Fastfile describes lanes — sequences of actions. Typical iOS configuration:

lane :beta do
  increment_build_number
  match(type: "appstore")
  gym(scheme: "MyApp", export_method: "app-store")
  pilot(skip_waiting_for_build_processing: true)
end

Match is the key to managing certificates and provisioning profiles. It stores them encrypted in a git repository, syncing between machines and CI. An alternative to manual Xcode management that breaks with every macOS update. Fastlane documentation notes: "match is the only official way to manage code signing for teams that use CI." Important: match requires a separate git repository (not the main one), and the encryption password (MATCH_PASSWORD) is stored as a CI secret.

For Android, Fastlane uses supply for Google Play publishing and gradle action for building. Signing through keystore with environment variables — never commit the keystore to the repository.

The main pain of Fastlane: Ruby environment. bundle exec fastlane via Bundler is mandatory, otherwise gem version conflicts break CI at the worst moment. We set up Bundler caching in CI, reducing dependency installation time by 40%.

GitHub Actions for mobile

GitHub Actions is suitable if the repository is already on GitHub. For iOS, you need a macOS runner — runs-on: macos-14 (Apple Silicon). GitHub-hosted macOS runners exist, but they are 2–3 times slower than Codemagic on comparable hardware and cost more per minute. Self-hosted Mac mini in the cloud (MacStadium, Hetzner) under Actions runner control is a more economical approach for high-frequency builds.

Typical workflow for iOS:

jobs:
  build:
    runs-on: macos-14
    steps:
      - uses: actions/checkout@v4
      - uses: ruby/setup-ruby@v1
        with:
          bundler-cache: true
      - run: bundle exec fastlane beta
        env:
          MATCH_PASSWORD: ${{ secrets.MATCH_PASSWORD }}
          APP_STORE_CONNECT_API_KEY_KEY: ${{ secrets.ASC_API_KEY }}

App Store Connect API Key instead of Apple ID + password is mandatory. Apple ID with 2FA does not work reliably on CI. API Key is created in App Store Connect → Users and Access → Keys. We include creation and rotation of these keys in our work.

To set up GitHub Actions for iOS, follow these steps:

1. Create a YAML file in .github/workflows/
2. Configure repository secrets: MATCH_PASSWORD, ASC_API_KEY (key in JSON)
3. Set runs-on: macos-14
4. Use ruby/setup-ruby@v1 with bundler-cache: true
5. Run bundle exec fastlane beta

Why choose Codemagic or Bitrise for mobile CI?

Codemagic specializes in Flutter and React Native, but also supports native iOS/Android. Killer feature — codemagic.yaml configuration and macOS M2 machines without additional setup. Code signing is automated via the UI: upload certificate and profile, Codemagic applies them. Convenient for teams without DevOps. Builds on M2 run 2 times faster than on GitHub Actions Intel runners.

Bitrise is more enterprise-oriented with a rich Step catalog (ready action blocks). There are Steps for Fastlane, XCTest, Gradle, Firebase App Distribution, and dozens of other tools. The visual Workflow Editor lowers the entry barrier. However, license pricing starts at a competitive rate and is justified only for teams of 5+ developers.

What are the main stages of CI/CD setup?

Distribution: TestFlight, Firebase App Distribution, Diawi

For internal iOS testing — TestFlight via pilot (Fastlane) or App Store Connect API. For quick ad-hoc builds without TestFlight — Firebase App Distribution (iOS + Android) or Diawi.

Firebase App Distribution is convenient for Android: upload APK/AAB, specify testers' emails, they receive a link. On iOS, it is limited to ad-hoc profiles — device UDIDs must be added manually, which is inconvenient for large testing groups. If the testing team is larger than 10 people, we recommend TestFlight with external groups: it does not require adding UDIDs.

How to set up versioning without errors?

Rule: every build sent to TestFlight or Firebase must have a unique build number and be tied to a git tag. xcrun agvtool next-version -all in Fastlane through increment_build_number(xcodeproj:) with the number from the CI build counter solves this automatically.

Checklist of typical versioning mistakes:

• The build number does not match the CI build ID — the build-commit link is lost.
• Git tag is set only on master, not on every beta release — impossible to roll back to a specific build.
• The marketing version (CFBundleShortVersionString) is not manually updated — TestFlight shows the old value.

What is included in the work (deliverables)

We set up CI/CD end-to-end, and as a result you get:

• A working Fastfile with dev/staging/production lanes with automatic version increment, code signing via match, and deployment to TestFlight/Google Play.
• Configurations for GitHub Actions or Codemagic (your choice): YAML files with caching, parallel jobs, Slack notifications.
• App Store Connect API Key and push notification setup (APNs/FCM).
• Documentation on running builds and updating certificates.
• Team training: 2-hour online workshop on using the pipeline.
• Post-release support for 14 days (fixing any potential errors).

Why trust us with setup?

We are a team of mobile developers with 5+ years of experience in CI/CD. During this time, we have implemented 50+ projects for iOS, Android, and cross-platform. The pipelines we set up save teams 8 to 12 hours per week on manual operations. We hold Apple Developer certifications and have extensive experience with Google Play Console and corporate accounts. The investment in setup pays off in 2–3 months. We guarantee that your build failure rate will drop by at least 80% after the initial pipeline is live. Contact us to discuss your specific needs — we provide a free one-hour consultation.

Timelines and cost

Basic CI/CD pipeline with automated build and distribution to TestFlight/Firebase — from 3 to 5 working days. Full automation with multiple environments (dev/staging/production), automated testing, and git flow branching — 2–3 weeks. Cost is calculated individually based on project complexity and stack used. Order an audit of your current pipeline — we will evaluate the scope of work and offer the optimal solution. Get a consultation — contact us.