Google Play accepts Android App Bundle files, the .aab format, instead of individual APKs. The bundle contains everything Play needs to build device-specific APKs for each user. This guide walks the full path: configure signing, build the release bundle, and get it onto a track in Play Console where testers can install it.
Before you build
- A developer account with an app created in Play Console, even if it has never shipped.
- Enrollment in Play App Signing, which is required for new apps and gives you an upload key plus a Google-managed app signing key.
- A release signing config in Gradle pointing at your upload keystore.
- A version code that is higher than every version code ever uploaded to this app.
Build the signed bundle
Configure signing in Gradle
Add a signingConfigs block with your keystore path, alias, and passwords, ideally read from environment variables or a local properties file that stays out of version control.
Run the bundle build
Execute the Gradle bundle task for your release variant, commonly ./gradlew bundleRelease. Android Studio's Generate Signed Bundle menu does the same thing if you prefer a GUI.
Locate and verify the output
The build writes an .aab under your module's build outputs directory. Confirm the version code inside matches what you intend, and install a locally generated APK if you want a final sanity check on a device.
Upload to Play Console
Open a testing track first
In Play Console, go to your app's release area and start with the internal testing track. Uploading straight to production skips the cheap feedback that internal testing exists to give.
Drop in the bundle and add testers
Upload the .aab, let Play process it, then add tester emails or groups. Processing failures at this stage usually mean a signing mismatch or a version code that was already used.
Review, then release
Check the release summary, confirm the rollout plan, and publish. Testers get the listing link and can install once the release is live on the track.
The upload itself takes minutes; the surrounding decisions, track choice, version codes, and rollout plan, are what determine whether the release goes smoothly. Teams that ship often use AppsTestLab's release management so every bundle goes up the same tested way, on the same track sequence.
First upload coming up?
AppsTestLab can walk your bundle through internal testing and a staged production rollout, so your first release to Google Play is uneventful.
Talk to us on WhatsAppFrequently asked questions
Why does Play say my version code is already used?
Version codes must increase across every upload to the app, including test tracks. Bump the code and rebuild; if you need to know the highest used number, check the release history for your existing tracks.
Can I upload an APK instead of a bundle?
Play requires the Android App Bundle format for new apps and updates on modern Play Console. Build a signed .aab instead, since Play generates the device-specific APKs from it.
What do I do if Play rejects my bundle during upload?
Read the processing error: signing mismatches, malformed bundles, and reused version codes are the usual causes. Fix the build configuration, generate a fresh bundle, and upload again.
Sources & references
Official Google documentationThese links open Google's official Play Console Help pages used to verify this guide. AppsTestLab guidance is independent and not affiliated with Google.
Get help doing this
