Automating Build Distribution via Firebase App Distribution

Automating Build Distribution via Firebase App Distribution

When test builds need to reach the team before App Store or Google Play approve a release, every hour of waiting is downtime. Firebase App Distribution (FAD) solves this: it delivers .apk or .ipa directly to testers, bypassing moderation. But manual uploads via the web interface are also time-consuming, especially with multiple daily commits. We fully automate this process: from iOS signing via match to integration with GitHub Actions or GitLab CI. Turnkey setup with one month of support — investment from $1,500, saving 10+ hours per week.

FAD Advantages over TestFlight and Play Console

TestFlight requires Apple review enrollment and caps at 100 testers. Play Console is Android-only, and internal testing can be delayed by up to an hour. FAD offers up to 1000 testers per project, instant delivery, and built-in Crashlytics integration — crash reports appear immediately after installation. FAD delivers builds 5x faster than Play Console internal testing and reduces manual effort by 80%. Developers spend time on features, not waiting.

Setting Up Android Distribution via Fastlane

Fastlane is the standard CI/CD tool for mobile development. The firebase_app_distribution plugin makes distribution a single command. Follow these steps:

1. Install Fastlane and the plugin: gem install fastlane and fastlane add_plugin firebase_app_distribution.
2. Obtain a Service Account JSON key from Google Cloud IAM with Firebase App Distributor role.
3. Store the key and the Firebase App ID (1:123456789:android:abcdef) in CI secrets.
4. Define a lane:

lane :distribute_android do
  gradle(
    task: "assemble",
    build_type: "Debug",
    flavor: "staging"
  )

  firebase_app_distribution(
    app: ENV["FIREBASE_APP_ID_ANDROID"],
    service_credentials_file: ENV["FIREBASE_SERVICE_ACCOUNT"],
    groups: "qa-team, internal-testers",
    release_notes: "Branch: #{git_branch}\nCommit: #{last_git_commit[:message]}"
  )
end

Alternatively, use firebase login:CI for a token, but Service Account is recommended for CI.

iOS Setup: Ad-Hoc Signing and UDID

For iOS, the process is more complex due to provisioning profiles. You need an .ipa signed ad-hoc or development. Register tester devices in the Apple Developer Portal. Firebase automatically collects UDIDs via an onboarding link, but the profile must be rebuilt. Fastlane + match automate this too:

lane :distribute_ios do
  match(type: "adhoc", readonly: true)

  build_app(
    scheme: "MyApp-Staging",
    export_method: "ad-hoc"
  )

  firebase_app_distribution(
    app: ENV["FIREBASE_APP_ID_IOS"],
    service_credentials_file: ENV["FIREBASE_SERVICE_ACCOUNT"],
    groups: "ios-testers",
    release_notes: "Build #{build_number}"
  )
end

Fastlane documentation: firebase_app_distribution plugin

When adding a new tester, import their UDID via the generated FAD link — firebase appdistribution:testers:invite or through the interface. Then update the profile. match with the register_devices option does this automatically on the next build.

Firebase App ID: Don't Mix Them Up

FIREBASE_APP_ID is not the bundle identifier; it is a string like 1:123456789:android:abcdef. Get it from Firebase Console → Project Settings → Your apps. A common mistake is using the Android ID for iOS, or vice versa.

CI Integration Without Fastlane

If the project does not use Fastlane, Firebase CLI works directly:

firebase appdistribution:distribute app-release.apk \
  --app "$FIREBASE_APP_ID" \
  --groups "qa-team" \
  --release-notes "Automated build $CI_BUILD_NUMBER" \
  --token "$FIREBASE_CLI_TOKEN"

This command suits any CI: GitHub Actions, GitLab CI, Bitrise, CircleCI. The only difference is how the token is passed — via environment variables.

Comparison: Fastlane vs Firebase CLI

What's Included in Turnkey Setup

• Analysis of current CI and build stack.
• Create Firebase project or configure an existing one.
• Create a service account in Google Cloud IAM.
• Write Fastlane lanes or shell scripts for both platforms, including iOS signing.
• Integrate with GitLab CI, GitHub Actions, or Bitrise.
• Configure tester groups (QA, Internal, Alpha).
• Test run, verify notification delivery.
• Documentation for developers and QA engineers.

Timeline: 1 to 3 days depending on signing complexity and number of platforms. We guarantee support for 30 days after delivery: adapt scripts to your changes. With 5+ years of experience in mobile CI/CD and over 50 successful integrations, we ensure reliable automation.

For more details, contact us for a free initial consultation. The investment in automation pays off by accelerating cycles — every build is delivered 5 times faster, reducing manual effort costs by up to 60%.

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.