How to Publish Your Flutter App (.AAB) to Google Play in 2026 Without 20 Testers
Flutter developers frequently hit two roadblocks when launching on Google Play: the 14-day / 12-tester closed testing wall on new personal accounts, and hidden AndroidManifest permissions injected by `pub.dev` packages (`image_picker`, `geolocator`, `permission_handler`). PlayGate handles your entire Flutter release from `.aab` preflight to 24-hour Play Console transfer.
- •Transitive `pub.dev` plugins injecting `READ_MEDIA_IMAGES` or `REQUEST_INSTALL_PACKAGES` into the merged AndroidManifest.xml.
- •Missing Data Safety declarations when using `firebase_core`, `firebase_crashlytics`, or `google_mobile_ads`.
- •Debug signing configuration accidentally left in `android/app/build.gradle` instead of a release upload keystore.
- Run `flutter build appbundle --release` signed with your private upload `.jks` keystore.
- Verify `applicationId` in `android/app/build.gradle` starts with `com.` and matches your target package name.
- Ensure `targetSdkVersion` is set to 34 or 35 (Android 14/15 compliance).
- Compile your initial $75 Transfer build without active AdMob banners so review clears rapidly.
1. Why Flutter Apps Get Flagged in Automated Google Play Bytecode Scans
When Gradle compiles your Flutter project into an `.aab`, it merges the `AndroidManifest.xml` files of every plugin in your `pubspec.yaml`. Even if your Dart code never calls camera or storage APIs, a single helper package can inject restricted permissions that trigger an immediate policy rejection. Our pre-flight audit inspects your compiled `.aab` manifest before uploading to Google.
2. Skip the 14-Day Closed Test & Transfer Straight to Your Console
Instead of recruiting 12 testers for 14 days on a new personal account, upload your signed Flutter `.aab` on Step 1 (/order). We clear Google Play Production review on our established developer console and transfer the live Flutter app to your 19-digit Developer ID within 24 hours.
Flutter & Dart Publishing FAQ
Do you need my Flutter source code or only the compiled .aab?
We only need your compiled, release-signed `.aab` file (`build/app/outputs/bundle/release/app-release.aab`). Your Dart source code and private upload keystore remain 100% on your machine.