OOmnistu

Blog / Engineering Playbooks

Engineering Playbooks

CI/CD for mobile apps: GitHub Actions plus fastlane, without release-day drama

Who owns what between a general CI platform and a mobile release tool, a three-workflow starter shape, and the signing, versioning and runner-cost traps that bite first.

OOmnistu
Reviewed 2026-11-19 · 4 min read

A mobile release has more moving parts than a web deploy: two platforms, code signing on each, screenshots, store metadata, review queues and staged rollouts. Doing those steps by hand is fine until it is not - usually the night a hotfix has to ship. Continuous integration and delivery (CI/CD) moves the repetitive parts into a pipeline that runs the same way every time. This guide covers the two tools most small app teams actually combine: GitHub Actions for the general automation, and fastlane for the mobile-specific steps.

What each tool owns

GitHub describes Actions as a continuous integration and continuous delivery platform that automates your build, test and deployment pipeline. A pipeline is a workflow: a YAML file in your repository that runs in response to an event (a push, a pull request, a tag, or a manual trigger). Each workflow contains jobs, each job runs on a runner, and each job is a sequence of steps that call actions or shell commands.

fastlane describes itself as the easiest way to automate beta deployments and releases for iOS and Android apps, and it handles the tedious mobile tasks: generating screenshots, dealing with code signing and releasing your application. You define those steps in a Fastfile in your repository as named lanes, built from built-in and community actions. A lane might build a signed release bundle, upload it to TestFlight or the Play Console and post the build number to your chat.

The clean split for a small team: GitHub Actions decides when things run and provides the machine; fastlane knows how to do the mobile work on that machine. Your workflow calls fastlane beta; the lane does the signing, building and uploading.

A starter shape that works

Keep three workflows rather than one giant one:

The mobile-specific traps

Code signing belongs in secrets, not the repo. Certificates, keystores and API keys live in your CI system's secret store and are written to disk only inside the runner. fastlane's match approach keeps iOS signing assets in a separate private repository or cloud storage so every runner gets the same identities; on Android, keep the upload keystore out of the app repository entirely and store its passwords separately from the file.

Version codes must move forward. Both stores reject uploads whose version code is not higher than what is already live. Derive the build number from CI (run number or commit count) rather than bumping it by hand, and record it in your release notes so a crash report can be traced back to the exact commit that built it.

Cache aggressively. Gradle and CocoaPods dependencies dominate mobile build times. GitHub Actions supports dependency caching between runs; using it is often the difference between a 6-minute and a 20-minute pipeline.

Runners cost money on iOS. macOS runners are the expensive part of any iOS pipeline. Run iOS builds on the workflows that need them and keep everything else on Linux.

Start smaller than you think

A first pipeline that runs tests on every pull request and produces one signed internal build per merge already removes most release-day risk. Add store upload automation only after the signing and versioning steps have run cleanly for a few weeks. The goal is not an impressive diagram; it is that nobody on the team can remember the last release that depended on one person's laptop.

Sources

Prepared with AI assistance and reviewed before publication. Tool capabilities described from the projects' own documentation, checked on 19 November 2026.