Setup guides
Closed testing, framework by framework.
The Play Console part is the same for every app. What differs is how you build, sign and version the bundle. Pick your framework for exact commands, menus and the mistakes that cost testers days.
Pick your framework
- FlutterRelease bundle, key.properties signing, the build number in pubspec.yaml, flavors and obfuscation.
flutter build appbundleRead the guide - React NativeGradle release bundle, upload keystore in gradle.properties, Hermes, R8/ProGuard and versionCode.
./gradlew bundleReleaseRead the guide - ExpoEAS production build, EAS-managed credentials, remote versionCode, eas submit to the closed track.
eas build -p android --profile productionRead the guide - UnityBuild App Bundle (Google Play), Keystore Manager, IL2CPP with ARM64, Bundle Version Code and Target API Level.
Build App Bundle (Google Play)Read the guide - Kotlin / Jetpack ComposeGradle bundleRelease, signingConfigs in build.gradle.kts, R8 keep rules, versionCode and targetSdk.
./gradlew bundleReleaseRead the guide - Ionic / CapacitorWeb build, npx cap sync android, Generate Signed Bundle in Android Studio, variables.gradle and Capacitor's target SDK.
npx cap sync androidRead the guide - GodotExport templates, Gradle build, AAB export format, release keystore, Version Code and Target SDK.
Export Format: AAB (Use Gradle Build)Read the guide
The same five steps, whatever you build with
Every guide follows this path to production access. Only step one depends on your framework.
Build a signed .aab
Release build, your upload key, Play App Signing, a fresh version code and target API level 36.
Publish to closed testing
Upload to the closed track, choose countries, send for review and wait for Published.
Get 12 testers opted in
Add a Google Group under Testers and share the opt-in link.
Keep them for 14 days
Daily use, real feedback and at least one update during the test.
Apply for production
Dashboard → Apply for production: three sections about your test, your app and your readiness.
The full Play Console walkthrough
Closed track, Google Group and opt-in link, the 12 testers / 14 days rule and the production application, step by step on one page.
New to the 12 testers rule?
The general guide explains Google's requirement, how a TestBunny campaign runs day by day and what we can and can't guarantee.
Need 12 real testers for 14 days?
Add your app and closed testing link, pick Starter (15 testers) or Pro (25 testers), and follow every tester's activity day by day in your panel.
TestBunny isn't affiliated with Google. Testers earn credits, never cash. Nobody can guarantee Google's production access decision, and we don't.