skip to content

Firebase Distribution

Getting pre-release Android and iOS builds to named testers: tester groups, release notes and ad hoc iOS profiles. A release-process question about how QA and stakeholders get a build in hand.

on this pageshow

explore

questions

6

What is Firebase App Distribution for, and how does an invited tester get a pre-release Android build onto a device?

level: juniorimportance: should knowfreq 35%

answer

  1. builds before the store
  2. upload, pick testers, Distribute
  3. email invite, sign in with Google
  4. App Tester app installs the build
  5. invite expires, release expires

basics

~20 s

Firebase App Distribution gets pre-release Android and iOS builds to named testers. You upload a build, choose testers or groups, add release notes and Distribute; testers accept the emailed invitation with a Google Account and install from the App Tester app.

solid answer

~40 s

Firebase App Distribution is Firebase's channel for getting pre-release builds (APK, AAB or IPA) to people you name, without a store listing or review. On the developer side you register the app with the same package name, open App Distribution and click **Get started**, then upload a build signed with your debug key or app signing key, choose tester groups and individual testers, add release notes and click **Distribute**. New testers get an invitation email, existing ones a new-build email. On Android the tester opens the invitation, signs in with a Google Account, accepts, and installs through the **Firebase App Tester** app, allowing installs from that source the first time. Invitations expire after 30 days unaccepted; a release stays available for 150 days.

go deeper

for a junior

Recall the loop: upload a signed build, choose testers or groups, add release notes, Distribute; the tester accepts by signing in with Google and installs from the App Tester app.

for a middle

Explain the limits that shape a test programme: 30-day invitations, 150-day releases, 1,000 releases per app, and 500 testers per project with 200 per group.

for a senior

Show you can untangle tester problems: a different accepting account, an invitation never accepted, a signature mismatch on update, a package name that differs from the registered app.

for a principal

Frame App Distribution as the private, review-free pre-release channel and say which audiences belong in it and when a build should instead go through the store's own testing.

## What Firebase App Distribution is **Firebase App Distribution** is a Firebase service for getting **pre-release builds** of an app onto the devices of people you choose: QA engineers, a product manager, a client reviewing a feature. It handles Android (`.apk` and `.aab`) and iOS (`.ipa`) builds from the same console, so one team can manage both platforms' test builds in one place. It is deliberately not a store. There is no listing, no review queue and no public discovery: a build reaches only the testers you invite. Testers do not need an SDK in the app to install a build; the SDK is optional and only adds in-app extras such as new-build alerts. ## The developer side: one release 1. **Register the app** in a Firebase project with exactly the package name you ship. The package name is case-sensitive and cannot be changed after registration, so a debug variant with a different application ID needs its own Firebase app. 2. Open the App Distribution page in the Firebase console, pick the app and click **Get started**. 3. **Build and sign** the binary. An Android APK must be signed with your debug key or your app signing key; an unsigned APK fails to upload. 4. On the **Releases** page, drag the file in (or upload it from the Firebase CLI or the Gradle plugin; the console is just the manual path). 5. Choose **tester groups** and **individual testers**, write **release notes**, and click **Distribute**. Each distributed build is a **release**. The console shows, per tester, whether they accepted the invitation and whether they downloaded that release, and the link icon copies a release link you can share with testers who already have access. ## The tester side on Android - **Invitation email.** A tester who has never been invited gets an invitation; an existing tester gets a "new build ready" email instead. - **Sign in with Google and accept.** The tester can sign in with any Google Account, not only the address the invite went to, and an invitation can be accepted only once. A Google Account can be tied to a non-Gmail address, so a work email works too. - **Firebase App Tester.** After accepting, the tester is prompted to install the Firebase App Tester app (also available from `appdistribution.firebase.google.com` on the device). It lists every test app the tester has access to; tapping **Download** installs the build. - **Unknown sources.** Because the build does not come from Google Play, Android asks the tester to allow installs from App Tester or the browser the first time (on Android 8 and later, "Allow from this source"). - **App bundles** need one more one-time step, turning on internal app sharing in the Play Store app's settings, because Google Play delivers AAB releases. ## Timers and limits worth knowing | Item | Value | |---|---| | Invitation validity | 30 days to accept; a notice shows 5 days before expiry; resend from the tester row | | Release availability | 150 days from upload; a notice shows 30 days before expiry | | Releases per app | 1,000; the oldest above the limit are deleted | | Testers | 500 per Firebase project, 200 per group (a no-cost increase can be requested) | | Binary size | 2,048 MiB maximum | When a release expires it disappears from the console and App Tester, but a copy already installed on a device keeps running. ## What commonly goes wrong - **Accepted with a different account.** If the invite went to address A and the tester accepted as account B, App Distribution links them: adding A to later releases gives B access, but notification emails still go to A. When the tester sees the wrong apps, delete the tester and re-invite, and have them accept with the invited address. - **Never accepted.** A tester who ignored the first invitation is not sent release notifications for later releases they are added to. - **Update will not install.** Android installs an update only when its signing certificate matches the installed copy, so builds signed with different debug keys on different machines collide; also check `minSdkVersion` against the tester's OS version. - **Package name mismatch.** If the uploaded APK's package does not match the Firebase app, App Tester may not show the app as installed. The service fits the moment between "it works on my machine" and a store release: quick, private, per-person access to exactly the build under test.

  • A tester was invited at their work address but accepted with a personal Google Account; what happens in Firebase App Distribution?
    App Distribution links the two: whenever the invited address is added to a release, the account that accepted gets access. Notification emails still go to the invited address, though, and the tester may not see the right apps or builds. The fix is to delete the tester under Testers & Groups, which removes existing invitations, re-invite them, and have them accept with the address the invitation was sent to.
  • A tester's new App Distribution build fails to install over the previous one; what do you check first?
    Signing first: Android only updates an installed app when the new build's certificate matches, so two CI machines with different debug keystores produce builds that cannot replace each other. Share one debug keystore or sign with the app signing key. Then check that the tester's OS version meets the app's `minSdkVersion`. Uninstalling the old copy works as a one-off but loses the tester's local data.

  • Testers need a Google Play developer account to install builds.
  • Testers can only install after the app adds the App Distribution SDK.
  • A distributed release stays available to testers indefinitely.
  • An unsigned APK is fine because App Distribution signs it on upload.
  • One invitation link can be accepted again and again by anyone.
open as a page

In Firebase App Distribution, how does CI upload a nightly Android build to tester groups with release notes, via the CLI or Gradle plugin?

level: middleimportance: should knowfreq 30%

basics

~10 s

CI runs firebase appdistribution:distribute with --app, --groups and --release-notes-file, or the Gradle plugin's appDistributionUploadRelease task configured in a firebaseAppDistribution block, both authenticated with a service account holding the Firebase App Distribution Admin role.

open as a page

In Firebase App Distribution, an iOS tester accepted the invite but cannot install your ad hoc build; what is missing and how do you fix it?

level: seniorimportance: should knowfreq 25%

basics

~20 s

The device's UDID is not in the ad hoc provisioning profile. Export the registered UDIDs from App Distribution, add the devices in the Apple developer account and to the profile, rebuild with the same version and build number, and redistribute.

open as a page

As a lead, would you make Firebase App Distribution or Play's internal testing track the team default for Android pre-release builds, and why?

level: principalimportance: should knowfreq 30%

basics

~20 s

Usually App Distribution for day-to-day builds and Play's internal testing track for release candidates. App Distribution takes any signed variant on both platforms for up to 500 testers; the internal track delivers the store-signed bundle through Google Play to at most 100.

open as a page

Your beta Android build calls the Firebase App Distribution SDK's updateIfNewReleaseAvailable, yet a tester never sees a new-build alert; how do you diagnose it?

level: seniorimportance: nice to knowfreq 15%

basics

~20 s

Confirm the beta variant ships the full firebase-appdistribution SDK, not just the API library; log the Task's FirebaseAppDistributionException; check the Firebase App Testers API is enabled and allowed by the API key; and check the tester accepted the release with that account.

open as a page