Will Play accept this bundle?
Check an .aab before you upload it. See the upload key, target API, modules and permissions, and catch the problems Play Console rejects.
Drop your .aab
or browse files. Any size works
Read on your device. Nothing is uploaded.
Why Play rejects a bundle
These are the upload errors the inspector looks for. Each one shows up as a red line above the details, with what to change.
- 1
Signed with the wrong key
Play Console only takes bundles signed with your upload key. The inspector shows the upload certificate's SHA-256 so you can compare it with the one under Setup, App signing, and flags the debug key straight away.
- 2
Built as debuggable
A debug build, or a manifest with android:debuggable set, is turned down on upload.
- 3
Target API too low
New apps and updates have to target API 36 or higher.
- 4
Not ready for 16 KB pages
Since November 2025, Play requires every 64-bit native library in apps targeting Android 15 and up to be aligned to 16 KB. The inspector names each library that isn't.
- 5
No 64-bit code
Bundles with 32-bit native libraries need arm64-v8a versions too.
- 6
Permissions that need a declaration
SMS, call log, all files access, background location and a few others are held back until you fill in a declaration in Play Console.
Want to try the build on a phone first? Convert the AAB to an APK and share it with your testers.
Questions
Do you upload my bundle?
No. The .aab is read inside your browser tab. We read the manifests, the zip directory and the headers of the native libraries, and nothing is sent to us. A huge bundle checks as fast as a small one.
Is the SHA-256 shown the one my users will see?
No, and that's on purpose. A bundle is signed with your upload key. With Play App Signing, Google re-signs the APKs it delivers with a separate app signing key that only Play holds. Use this fingerprint to check you're uploading with the right key. For Firebase, Google sign in and Maps, register the app signing key from Play Console as well.
Play says "You uploaded an APK or Android App Bundle that was signed in debug mode".
Your release build is using the debug signing config. In Flutter that's the default signingConfig in android/app/build.gradle until you change it. Point the release build type at your upload keystore, rebuild, and check the bundle here: the warning disappears when it's right.
How do I fix the 16 KB warning?
Update to Android Gradle Plugin 8.5.1 or newer and NDK r28 or newer, then rebuild. If the library named in the warning comes from a dependency, such as an SDK or a Flutter or React Native plugin, update that dependency. Most popular ones shipped 16 KB builds during 2025.
Why is the bundle so much bigger than the app on Play?
The bundle holds every language, screen density and CPU architecture, and Play sends each phone only what it needs. It can also carry debug symbols and a mapping file, which stay with Play. The size breakdown separates those out.
Can I install the bundle to test it?
Not as it is. Phones only install APKs. The AAB to APK converter turns it into one signed APK you can install on any phone.