Mobile · Open-source build
Automated mobile release train
From merged pull request to signed builds in both stores' test tracks with nobody touching Xcode or a keystore.
What it is
Fastlane lanes handle certificates, provisioning, versioning, screenshots and store upload. Signing material lives in an encrypted repository managed by match. Every merge to main produces a build in TestFlight and the Play internal track; a tagged release promotes to production with staged rollout and automatic halt on crash-rate regression.
What the build consists of
- 01Fastlane match for certificates and profiles shared safely across the team
- 02Lanes for beta, release and screenshot generation in every locale
- 03GitHub Actions runners for iOS and Android with cached dependencies
- 04Staged rollout with a crash-rate guard that halts the release
- 05Changelog assembled from pull request titles
What you see in a demo
Merging a pull request and, twenty minutes later, installing the build from TestFlight on a phone. Then a rollout halting itself when a crash is injected.