Short answer
A mobile CI/CD pipeline builds the iOS and Android apps on every change, signs them with keys stored as CI secrets, bumps build numbers, runs tests and uploads to TestFlight and the Play internal track. For apps written by coding agents it is also the main quality gate, so keep signing and release steps out of the agent's reach.
On this page
Why mobile pipelines matter more with AI
Coding agents such as Claude Code, Codex and Cursor can produce a React Native, Flutter or native change in minutes. The slow part is no longer writing code; it is building, signing, distributing and checking it on real devices. Without automation, a team that generates ten changes a day still ships one build a week, because someone has to open Xcode, archive, upload and wait.
Mobile CI/CD closes that gap, and it does something else that matters with agents: it applies the same checks to every change, regardless of who or what wrote it.
What the pipeline needs to do
| Stage | iOS | Android |
|---|---|---|
| Check out and install | Ruby or Node toolchain, CocoaPods or Swift Package Manager | JDK, Gradle |
| Static checks | Lint, type-check (for RN or Flutter) | Lint, type-check |
| Tests | Unit tests, optional UI tests on simulator | Unit tests, optional instrumented tests on emulator |
| Version | Increment build number | Increment version code |
| Sign | Distribution certificate and provisioning profile | Upload key, Play App Signing |
| Build | Archive to IPA | Bundle to AAB |
| Distribute | Upload to TestFlight | Upload to internal testing track |
| Promote | Submit for review (manual trigger) | Promote to production (manual trigger) |
Choosing the tooling
There are several solid combinations:
- GitHub Actions or GitLab CI with fastlane. Flexible and widely documented. iOS builds need macOS runners.
- Dedicated mobile CI services such as Bitrise, Codemagic or Xcode Cloud. They take care of macOS machines and often simplify signing, especially for Flutter or React Native.
- Expo Application Services for Expo-based React Native apps, which handle builds, credentials and store submission in one place.
The choice matters less than consistency. Pick one, document it in your AGENTS.md or CLAUDE.md so agents know how builds work, and avoid parallel manual processes.
Code signing without pain
Signing is where most mobile pipelines fail. Keep it predictable:
iOS:
- Create an App Store Connect API key with a limited role for uploads, rather than using a personal Apple Account with two-factor prompts.
- Store the distribution certificate and provisioning profile encrypted, either via fastlane match in a private repository or in your CI provider's secure storage.
- Use automatic or explicit profile selection, but never rely on a developer's local keychain.
Android:
- Enable Play App Signing so Google manages the app signing key.
- Store only the upload keystore and its passwords as CI secrets.
- Use a Google Cloud service account with release permissions for the specific app to upload builds.
Document expiry dates. An expired iOS distribution certificate or profile breaks builds suddenly, often on release day.
Versioning
Stores reject uploads with a build number they have already seen. Let CI set the build number from the pipeline run number or a timestamp, and keep the human-readable version (1.4.0) in source control, changed deliberately for releases.
Guardrails for agent-written code
When an agent writes most changes, the pipeline is where you enforce rules that the agent might forget:
- Fail the build if the bundle identifier, package name, entitlements or permissions change without an explicit label on the pull request.
- Fail if new permissions appear in
Info.plistorAndroidManifest.xml; they need privacy declarations and store justification. - Run a secret scanner, since agents sometimes add API keys to config files for convenience.
- Never give the agent's own environment access to signing keys or store credentials. Agents write and fix pipelines; the pipeline holds the keys.
Wrapped web apps need CI too
If your mobile app is a native shell around a web app, built for example with WebViewGold, most changes deploy through your web pipeline and need no app build at all. You still want CI for the native side, because the app needs rebuilding for target API level updates, new iOS SDK requirements, changed push configuration or new native features. A small pipeline that builds both platforms from the template project on demand keeps those rare releases routine instead of a scramble.
From internal track to production
Automate everything up to the testing tracks; keep the step to production deliberate:
- Merge to main builds and uploads to TestFlight internal and Play internal testing.
- A release tag submits the build for App Store review and promotes it to a Play staged rollout.
- A person decides when to release after approval, ideally with phased release on iOS and a percentage rollout on Android.
- Crash and error monitoring for the new version is watched for the first days before widening the rollout.
Store metadata such as release notes, screenshots and descriptions can also live in the repository and be uploaded by the pipeline, which keeps listings in sync with features.
A realistic setup effort
For an existing React Native, Flutter or native project, expect a few days to get a reliable pipeline for both platforms, most of it spent on signing and store access. A wrapped web app is quicker because the native project is simpler.
appsubmitter.io sets up exactly this: CI/CD with signing, versioning and automated uploads to TestFlight and Google Play, built inside your own developer accounts and repository, plus listing management and help with rejections. Once the pipeline exists, appsubmitter.io can keep handling submissions while your team or your agents focus on features. For apps that need continued native development, apprat.io combines AI-assisted development with human developer hours and works inside the same pipeline.
Before setting up CI, make sure your developer accounts are set up as a company. For distributing the resulting builds, see TestFlight and Play Console internal testing; for the web side of agent-built apps, deploying a Claude Code app to production.
FAQ
Do I need a Mac for iOS CI/CD?
The build itself requires macOS and Xcode, but you do not need your own Mac. Hosted CI services provide macOS runners.
Is fastlane still the standard for mobile CI?
It remains widely used for signing, building and uploading. Mobile-focused CI services and Expo's build service are popular alternatives that wrap similar steps.
Should AI coding agents have access to signing keys?
No. Keep signing keys and store credentials only in the CI system's secret storage. Agents can edit pipeline files through reviewed pull requests.
Can CI submit my app for review automatically?
Yes, uploads and review submissions can be automated. We recommend a manual trigger for production submissions and releases.