If you aren't using any other Firebase products, you only have to create a
project and register your app. However, if you decide to use additional
products in the future, be sure to complete all of the steps on the page
linked above.
Step 1. Build your app
When you're ready to distribute a pre-release version of your app to testers,
build your APK using your normal process. You must sign the APK with your debug
key or app signing key.
Step 2. Distribute your app to testers
To distribute your app to testers, upload your APK file using the
Firebase console:
Open the App Distribution page of the
Firebase console. Select your Firebase project when prompted.
On the Releases page, select the app you want to distribute from
the drop-down menu.
Drag your app's APK file to the console to upload it.
When the upload completes, specify the tester groups and individual testers
you want to receive the build. Then, add release notes for the build.
Click Distribute to make the build available to testers. The tester
automatically receives an email invitation to test the app.
(Optional) To share links to specific releases with testers who have access
to those releases, click the
Link icon to copy the release link to the clipboard.
Once you distribute your build, it becomes available in the
App Distribution dashboard of the Firebase console for 150 days (five months).
When the build is 30 days from expiring, an expiration notice appears in both
the console and your tester's list of builds on their test device.
Testers who haven't been invited to test the app receive email invitations to
get started, and existing testers receive email notifications that a new build
is ready to test. For instructions on how to install the test app, see
Get set up as a tester with App Distribution.
You can monitor the status of each tester-whether they accepted the
invitation and whether they downloaded the app-in the Firebase console.
Testers have 30 days to accept an invitation to test the app before it expires.
When an invitation is 5 days from expiring, an expiration notice appears in the
Firebase console next to the tester on a release. An invitation can be
renewed by resending it using the drop-down menu on the tester row.
Next steps
Implement in-app feedback
to make it easy for testers to send feedback about your app (including
screenshots).
Learn how to display in-app alerts
to your testers when new builds of your app are available to install.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-15 UTC."],[],[],null,["\u003cbr /\u003e\n\nAPK AAB \n\n\u003cbr /\u003e\n\nThis guide describes how to upload APKs to App Distribution and distribute builds\nto testers using the Firebase console.\n\nBefore you begin\n\nIf you haven't already, [add Firebase to your Android\nproject](/docs/android/setup#console).\n\nIf you aren't using any other Firebase products, you only have to create a\nproject and register your app. However, if you decide to use additional\nproducts in the future, be sure to complete all of the steps on the page\nlinked above.\n| **Caution:** When you register your app with Firebase, make sure to enter the same package name as the app you're distributing. The package name value is case-sensitive and cannot be changed for your app in Firebase after it's registered with your Firebase project.\n\nStep 1. Build your app\n\nWhen you're ready to distribute a pre-release version of your app to testers,\nbuild your APK using your normal process. You must sign the APK with your debug\nkey or app signing key.\n\nStep 2. Distribute your app to testers\n\nTo distribute your app to testers, upload your APK file using the\nFirebase console:\n\n1. Open the [App Distribution page](https://console.firebase.google.com/project/_/appdistribution) of the\n Firebase console. Select your Firebase project when prompted.\n\n2. On the **Releases** page, select the app you want to distribute from\n the drop-down menu.\n\n3. Drag your app's APK file to the console to upload it.\n\n4. When the upload completes, specify the tester groups and individual testers\n you want to receive the build. Then, add release notes for the build.\n\n See [Manage testers](/docs/app-distribution/manage-testers) for more on\n creating tester groups.\n5. Click **Distribute** to make the build available to testers. The tester\n automatically receives an email invitation to test the app.\n\n6. (Optional) To share links to specific releases with testers who have access\n to those releases, click the\n **Link** icon to copy the release link to the clipboard.\n\nOnce you distribute your build, it becomes available in the\nApp Distribution dashboard of the Firebase console for 150 days (five months).\nWhen the build is 30 days from expiring, an expiration notice appears in both\nthe console and your tester's list of builds on their test device.\n\nTesters who haven't been invited to test the app receive email invitations to\nget started, and existing testers receive email notifications that a new build\nis ready to test. For instructions on how to install the test app, see\n[Get set up as a tester with App Distribution](/docs/app-distribution/get-set-up-as-a-tester?platform=android).\nYou can monitor the status of each tester-whether they accepted the\ninvitation and whether they downloaded the app-in the Firebase console.\n\nTesters have 30 days to accept an invitation to test the app before it expires.\nWhen an invitation is 5 days from expiring, an expiration notice appears in the\nFirebase console next to the tester on a release. An invitation can be\nrenewed by resending it using the drop-down menu on the tester row.\n\nNext steps\n\n- Implement [in-app feedback](/docs/app-distribution/collect-feedback-from-testers)\n to make it easy for testers to send feedback about your app (including\n screenshots).\n\n- Learn how to display [in-app alerts](/docs/app-distribution/set-up-alerts?platform=android)\n to your testers when new builds of your app are available to install.\n\n- Learn best practices for [distributing Android apps to QA testers using CI/CD](/docs/app-distribution/best-practices-distributing-android-apps-to-qa-testers-with-ci-cd)."]]