GoPlayTester

Play Console how-to

Uploading your first app bundle (AAB) to a closed testing release

October 5, 2026 · 4 min read

A software developer working on code at a dual monitor setup in a modern office.
Photo by Zayed Hossain on Pexels

Your first closed testing release needs a signed Android App Bundle (AAB) that targets a recent enough API level, plus Play App Signing set up on that first upload. Once the bundle is attached to the closed track and you send the release for review, Google checks it, and after approval your testers can install it. Here's how to get the upload right the first time.

If you haven't created the closed track yet, do that first with our step-by-step track setup.

Why an AAB and not an APK

Google says: "From August 2021, new apps are required to publish with the Android App Bundle" (About Android App Bundles). An AAB contains all your compiled code and resources, and Google Play builds optimized APKs for each device from it. For a new app, the AAB is the format to upload.

The compressed download size limit for an app bundle is 4 GB. Most apps are nowhere near this, but large games should check.

Before you build: three settings to check

1. Target API level

From August 31, 2026, new apps and app updates for phones and tablets "must target Android 16 (API level 36) or higher." An extension to November 1, 2026 can be requested. Wear OS and Automotive apps need API 35 or higher, and TV and XR apps need API 34 or higher (Target API level requirements).

Set targetSdkVersion (or targetSdk) in your Gradle build file. If it's too low, Play Console flags the release and you can't roll it out, so it's better to catch it now. Google may update these dates, so check the official page before each release.

2. Version code

Every bundle you upload needs a versionCode higher than any bundle previously uploaded for that app. Start at 1 for your first upload if you like, but remember each later build has to go up. The versionName (for example "1.0.0") is what users see and doesn't have to change in the same way.

3. Release build, not debug

Build a release variant (in Android Studio: Build > Generate Signed Bundle / APK, choose Android App Bundle). Debug builds are rejected. Remove test-only flags and point the app at the backend you want testers to use.

Play App Signing on your first upload

"When publishing your app to Google Play for the first time, you must also configure Play App Signing" (Sign your app). With Play App Signing:

  • You sign your bundle with an upload key you keep.
  • Google manages the app signing key used for the APKs delivered to devices.

When you create your first release, Play Console walks you through this. The simplest choice for most developers is to let Google generate and manage the app signing key. Keep your upload keystore and its passwords backed up somewhere safe; you'll need them for every future update.

Uploading to the closed track

  1. Open Test and release > Testing > Closed testing and click Manage track on your closed track.
  2. Create a new release.
  3. Confirm or set up Play App Signing if Play Console asks.
  4. Upload your .aab file. Wait for processing to finish.
  5. Check the release name. Play Console fills one in; you can keep it or use something like "1.0.0 closed test".
  6. Write release notes for testers. Keep them short: what the app does and what you'd like them to try.
  7. Save and click Next to review the release.

Read every error and warning on the review screen. Errors block the release. Warnings (such as missing deobfuscation files) don't block it, but they are worth fixing because they make crash reports easier to read.

Send it for review

Saving the release doesn't publish it. Go to Publishing overview and click Send for review. Closed releases are reviewed by Google, which can take a few hours or up to seven days, and longer in exceptional cases (Managed publishing). If nothing seems to happen, check you didn't skip this step; this article covers the most common cause.

Read the pre-launch report

The pre-launch report is "automatically generated when you upload an app bundle or APK." A crawler installs the app on test devices and taps, types and swipes through it, checking stability, Android compatibility, performance and accessibility. It's free, and results usually arrive within an hour, sometimes several hours (Pre-launch report).

If it shows crashes on startup, fix them and upload a new bundle before your testers start. A crash in the first minute is the fastest way to lose a tester's attention.

Common upload errors

  • "Version code has already been used." Increase versionCode and rebuild.
  • Target API too low. Raise targetSdkVersion to the current requirement and retest.
  • "You uploaded an APK or bundle signed in debug mode." Build a signed release bundle.
  • Wrong signing key. After your first upload, later bundles must be signed with the same upload key. If you lose it, Play Console has an upload key reset process.

Key takeaways

  • Upload a signed release AAB, not an APK or debug build.
  • Check target API level and version code before building.
  • Set up Play App Signing on the first upload and back up your upload key.
  • Send the release for review from Publishing overview, then read the pre-launch report.

Once the release is approved, the next job is getting at least 12 testers opted in for 14 continuous days. If you don't have them, GoPlayTester provides real testers on real devices; see the setup guide or order here.

Keep reading

All articles