AAB Generation
Android App Bundle (AAB) is the required publishing format for new apps on the Google Play Store, allowing Google to generate optimized, smaller APKs tailored to each user’s specific device.
Why AAB is Required
Unlike a universal APK containing resources for every device configuration, an AAB allows Google Play to deliver only the specific code and resources needed for each user’s device, reducing download size.
Generating a Release AAB
Locating the Generated AAB File
Signing Requirements for AAB
Just like APKs, the AAB file must be signed with your release keystore, using the same signing configuration set up in your build.gradle file.
Testing an AAB Locally with bundletool
Uploading to Google Play Console
The generated AAB file is uploaded directly through the Google Play Console when creating a new release, where Google automatically handles generating device-specific APKs.
Play App Signing
Google Play App Signing allows Google to manage your app’s signing key securely, letting you upload your AAB signed with an upload key while Google re-signs the final distributed APKs.
Conclusion
Generating a properly signed Android App Bundle is now the standard, required process for publishing React Native applications to the Google Play Store, replacing universal APK submissions.
