CI/CD for Mobile Apps with GitLab CI – Setup & Automation

CI/CD for Mobile Apps with GitLab CI – Build, Test & Deploy Automatically

Manual builds and deployments are a constant source of errors and wasted time. Statistics show up to 30% of development time goes into manual build and deploy operations. GitLab CI automates everything: every commit triggers a build, tests, and delivery to the stores. We've been setting up CI/CD end-to-end for over 5 years, ensuring stability and ongoing support. We'll assess your project in one day—just contact us.

GitLab CI is the optimal choice for teams already hosting their repository on GitLab (self-hosted or cloud). Configuration lives in .gitlab-ci.yml, and runners can be GitLab-managed or your own. For iOS builds you need a registered macOS self-hosted runner: standard GitLab SaaS plans only provide Linux/Windows runners. Compared to Jenkins, GitLab CI is simpler to set up—no separate server required—and comes with built-in registry, artifacts, and environments.

Problems Solved by GitLab CI

• Manual builds and signing lead to errors from mismatched profiles or forgotten certificates.
• No automated tests mean regressions slip into production.
• Slow store delivery—each release takes hours of manual work.
• Builds are not reproducible—local environments differ.
• Missing version control on artifacts makes rollbacks difficult.

GitLab CI solves all of these: builds are repeatable, tests run on every MR, and artifacts are tied to commits. In our experience, automation cuts release time by 40%.

Why a Self-Hosted macOS Runner Is Critical for iOS

Standard GitLab SaaS runners don't provide macOS, so iOS builds must use your own Mac. Registering a runner:

# On a Mac mini or MacBook that will be the CI machine
brew install gitlab-runner
gitlab-runner register \
  --url https://gitlab.com \
  --registration-token $RUNNER_TOKEN \
  --executor shell \
  --description "macos-m2-runner"
gitlab-runner start

executor shell – the runner executes commands directly in the shell, without a Docker container. For iOS this is the only realistic option because Xcode doesn't work inside Docker.

Important: the runner must run as a LaunchDaemon, not as a user process, otherwise CI stops after a reboot. Configure it with sudo gitlab-runner install --user runner. We use a Mac Mini M2 with 16 GB RAM—enough for parallel builds of two configurations. We guarantee 99.9% uptime.

Sample .gitlab-ci.yml for iOS + Android

stages:
  - test
  - build
  - distribute

variables:
  FASTLANE_SKIP_UPDATE_CHECK: "true"
  BUNDLE_PATH: vendor/bundle

.ios_job:
  tags:
    - macos-m2
  before_script:
    - bundle install --path $BUNDLE_PATH

.android_job:
  image: androidsdk/android-34
  tags:
    - linux-docker

ios:test:
  extends: .ios_job
  stage: test
  script:
    - bundle exec fastlane test
  artifacts:
    reports:
      junit: fastlane/test_output/report.junit
    paths:
      - fastlane/test_output/
    expire_in: 1 week
  rules:
    - if: $CI_PIPELINE_SOURCE == "merge_request_event"
    - if: $CI_COMMIT_BRANCH == "main"

ios:beta:
  extends: .ios_job
  stage: distribute
  script:
    - bundle exec fastlane beta
  environment:
    name: beta
  rules:
    - if: $CI_COMMIT_BRANCH == "main"
  needs: [ios:test]

android:build:
  extends: .android_job
  stage: build
  script:
    - ./gradlew test assembleRelease
  cache:
    key: $CI_COMMIT_REF_SLUG
    paths:
      - .gradle/
      - vendor/bundle
  artifacts:
    paths:
      - app/build/outputs/apk/release/
    expire_in: 3 days

Comparison of iOS and Android stages:

Code Signing Without Key Leakage

GitLab stores secrets in Settings → CI/CD → Variables. For iOS code signing we use:

before_script:
  - echo "$MATCH_KEYSTORE" | base64 -d > /tmp/match.keystore
  - bundle exec fastlane match adhoc --readonly true
  - echo "$ASC_API_KEY" > /tmp/AuthKey.p8
  - export APP_STORE_CONNECT_API_KEY_PATH=/tmp/AuthKey.p8

MATCH_KEYSTORE and MATCH_PASSWORD are masked variables in GitLab. Masked variables won't appear in logs even with echo. According to GitLab documentation, this approach prevents leakage.

For App Store Connect API Key—use a File-type variable with the .p8 file. With Fastlane match you can automatically update provisioning profiles when devices change or new developers are added.

Caching to Speed Up Builds

GitLab CI cache is key-bound. For CocoaPods:

cache:
  key:
    files:
      - Podfile.lock
  paths:
    - Pods/
    - vendor/bundle

Cache key based on Podfile.lock automatically invalidates when dependencies change. For Gradle use *.gradle* keys. This reduces build time by 40–60%.

Environments and Branch-Based Deployment

ios:staging:
  stage: distribute
  script:
    - bundle exec fastlane beta
  environment:
    name: staging
  rules:
    - if: $CI_COMMIT_BRANCH == "develop"

ios:production:
  stage: distribute
  script:
    - bundle exec fastlane release
  environment:
    name: production
  rules:
    - if: $CI_COMMIT_TAG =~ /^v\d+\.\d+\.\d+$/
  when: manual  # Requires manual approval in UI

when: manual for production creates a button in the GitLab UI as a gate before release. Useful when QA must approve before submitting to App Store. Production release is blocked until manual approval—standard practice for quality control.

What's Included in the Turnkey CI/CD Setup

When you order CI/CD setup, you get:

• A .gitlab-ci.yml file with test, build, and distribute stages for both iOS and Android.
• A configured self-hosted runner (macOS for iOS, Linux/Windows for Android).
• Integration with Fastlane for code signing and deployment to TestFlight / Google Play.
• Caching configuration for artifacts and dependencies.
• Environment definitions and rules for different branches and tags.
• Pipeline documentation and a 1-hour team training session.
• 2 weeks of post-launch support—we fix any issues that arise.

Timeline and Pricing

Basic setup (macOS runner, test + beta lanes): 3–5 days. Full configuration with environments, Android pipeline, caching, and review apps: 1.5–2 weeks. Pricing is individual.

Order your mobile app CI/CD setup today. We'll assess your project in one day—just contact us.

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.