Automating Build Distribution with AppCenter

Automating Build Distribution with AppCenter

We often see projects where manual distribution of test builds consumes 30% of the team's time. Developers spend hours uploading APK/IPA files to Slack or Telegram, mix up versions, and testers don't get notified about new builds. Each manual release takes 20–30 minutes on average; with 5 releases per week, that's 2.5 hours of pure loss. Typos in links and version mismatches force re-releases, stretching the test cycle by days. AppCenter (now part of Visual Studio Family) solves this: it combines distribution, crash reporting, and analytics in one service. In 1–3 days we set up an automatic distribution pipeline — from commit to installer on the tester's device.

How to Integrate AppCenter with CI/CD?

There are three main approaches: via Fastlane, AppCenter CLI, or the built-in Build Service. The choice depends on your current CI and flexibility needs. Fastlane gives 3–5x more control over the build: you can sign in parallel, run tests, and upload to multiple groups at once. Build Service is simpler but doesn't support custom Gradle scripts or multi-module projects — for complex apps, Fastlane is faster to set up.

Typical Setup Mistakes

Fastlane: The Main Pipeline

The appcenter plugin lets you upload builds directly from Fastlane. Android example:

lane :distribute do
  gradle(task: "assembleRelease")
  appcenter_upload(
    api_token: ENV["APPCENTER_API_TOKEN"],
    owner_name: ENV["APPCENTER_OWNER"],
    app_name: ENV["APPCENTER_APP_NAME_ANDROID"],
    file: lane_context[SharedValues::GRADLE_APK_OUTPUT_PATH],
    destinations: "QA-Team,Stakeholders",
    destination_type: "group",
    release_notes: "Branch: #{git_branch}, commit #{last_git_commit_hash}"
  )
end

Create the token in Account Settings → API Tokens. We recommend restricting access to a specific app — this reduces leak risks. For quick debugging, use AppCenter CLI: appcenter distribute release publish --file build.apk --app Owner/App --group testers.

What Pitfalls Exist for iOS Build Distribution?

iOS code signing is the most common issue. AppCenter requires an .ipa signed with an ad-hoc or enterprise profile. You can upload the certificate and profile in the Code Signing section, but when they change, you must update manually — there's no automatic sync with Apple Developer Portal. We recommend using Fastlane Match to manage certificates and link it to AppCenter via CI. This cuts setup time from 2 hours to 10 minutes.

AppCenter SDK supports mandatory updates: enable mandatory_update: true in the group settings — the app will then show a forced update screen until the user installs the new version. Useful for fixing critical bugs, e.g., when 98% of users are on an outdated version with a bug.

Groups and Notifications

AppCenter sends email notifications on new releases. You can create tester groups and assign different builds to different groups. For example, QA gets regression builds, stakeholders only stable versions. Configure notifications via webhooks — this integrates AppCenter with your corporate chat (Slack, Teams).

Scope of Work for AppCenter Setup

We offer turnkey setup:

• Create project and apps in AppCenter (iOS and Android)
• Generate API tokens with limited access
• Integrate with your CI (GitHub Actions, GitLab CI, Bitrise, Jenkins) — typical scenario takes 4–6 hours
• Configure Fastlane lanes for both platforms
• Set up tester groups and notifications
• Provide documentation on the distribution process
• Train your team (1–2 hours)

The process takes 1–3 days. Cost is calculated individually after analyzing your stack — contact us to get an estimate. Order a free consultation: we'll send a sample configuration for your project.

Why Trust Us with the Setup?

We've been in mobile development for over 5 years and have completed more than 30 projects with AppCenter. We know all the nuances of code signing, App Store Review Guidelines, and service limitations. We use proven Fastlane templates — ensuring pipeline stability. We'll assess your project for free and choose the optimal integration scheme.

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.