12 Testers for Any Framework: Complete Google Play Closed Testing Guide
Whether you use Flutter, React Native, Expo, Unity, Godot, Kotlin, or Ionic — Google Play's 12-tester, 14-day Closed Testing requirement applies to every Android app. This guide covers framework-specific AAB builds, Play Console setup, common issues, and how to get your 12 testers.
Does Google Play care what framework you use?
No. Google Play Console only sees the Android App Bundle (AAB) you upload. Whether that AAB was built by Flutter, React Native, Unity, or Kotlin is invisible to Google's review process. The 12-tester, 14-day Closed Testing requirement applies identically to every app, regardless of framework.
What does matter: your AAB must be properly signed, target the correct API levels, include 64-bit native libraries (if applicable), and not crash on real devices. These requirements are the same across all frameworks — but how you achieve them differs.
Below, find your framework for specific AAB build commands, Play Console setup steps, and the most common issues developers encounter — along with exactly how to fix them.
How Flutter developers get 12 testers for Google Play
Build command
flutter build appbundlePro tip
Run flutter clean before building. Verify your key.properties is configured for release signing.
Play Console setup steps
- 1.Run flutter build appbundle to generate your release AAB
- 2.In Play Console, go to Testing → Closed Testing → Create track
- 3.Upload your AAB — Play Console handles APK splitting automatically
- 4.Copy the opt-in URL from the "Testers" tab
- 5.Share the opt-in URL with your 12 testers (or paste it into TesterBee)
Common Flutter build issues and fixes
AAB size too large
Fix: Use --split-debug-info and enable ProGuard/R8 in android/app/build.gradle
Missing 64-bit native libraries
Fix: Ensure your build.gradle includes ndk.abiFilters "arm64-v8a", "x86_64"
Google Sign-In not working in testing
Fix: Add your testing SHA-1 fingerprint in Firebase Console
How React Native / Expo developers get 12 testers for Google Play
Build command
cd android && ./gradlew bundleRelease (or eas build for Expo)Pro tip
For Expo, use eas build --platform android to generate an AAB. The Expo dashboard handles signing.
Play Console setup steps
- 1.Build your AAB via ./gradlew bundleRelease (bare RN) or eas build (Expo)
- 2.Create a Closed Testing track in Play Console under Testing
- 3.Upload your signed AAB and complete the store listing
- 4.Copy the opt-in URL from the testers section
- 5.Distribute the link to your testers
Common React Native / Expo build issues and fixes
Hermes engine crashes on older devices
Fix: Test on API 24+ devices. Disable Hermes in build.gradle if needed for specific devices.
Metro bundler source maps in production
Fix: Set dev=false in your release build. Use react-native-bundle-visualizer to check size.
Expo EAS timeout during build
Fix: Use a paid EAS plan for priority builds or build locally with expo run:android --variant=release
How Unity developers get 12 testers for Google Play
Build command
File → Build Settings → Android → Build App Bundle (Google Play)Pro tip
Enable "Split Application Binary" in Player Settings → Publishing Settings to keep your AAB under Play Store size limits.
Play Console setup steps
- 1.In Unity, go to File → Build Settings, switch to Android platform
- 2.Check "Build App Bundle (Google Play)"
- 3.Configure Player Settings: package name, keystore, API levels (minimum 24)
- 4.Build the AAB and upload to Play Console Closed Testing track
- 5.Copy and share the opt-in URL
Common Unity build issues and fixes
AAB exceeds 200MB Play Store limit
Fix: Use Asset Bundles or enable Play Asset Delivery (PAD) in Player Settings
Gradle build fails
Fix: Enable "Custom Gradle Template" in Player Settings and update Gradle/AGP versions
Black screen on launch
Fix: Check that your first scene is set correctly in Build Settings → Scenes In Build
How Kotlin (Native Android) developers get 12 testers for Google Play
Build command
Build → Generate Signed Bundle / APK → Android App BundlePro tip
Use Android Studio's "Build → Analyze APK" tool to verify your AAB contents before uploading.
Play Console setup steps
- 1.In Android Studio: Build → Generate Signed Bundle / APK → Android App Bundle
- 2.Select your release keystore and enter signing credentials
- 3.Choose release build variant and build
- 4.Upload the AAB to Play Console → Testing → Closed Testing
- 5.Copy the opt-in URL and share with testers
Common Kotlin (Native Android) build issues and fixes
targetSdkVersion below Play Store minimum
Fix: Set targetSdkVersion to 34+ in app/build.gradle.kts
Debug certificate used in release build
Fix: Create a proper upload keystore and configure signing in build.gradle.kts
R8/ProGuard strips required classes
Fix: Add keep rules in proguard-rules.pro for libraries that use reflection
How Godot developers get 12 testers for Google Play
Build command
Project → Export → Android → Export ProjectPro tip
Set up a debug keystore first via Godot's Editor Settings → Export → Android, then switch to release keystore for production.
Play Console setup steps
- 1.In Godot: Project → Export, add an Android export preset
- 2.Configure the package name, keystore, and permissions
- 3.Export the project — Godot generates the AAB directly
- 4.Upload AAB to Play Console Closed Testing track
- 5.Share the opt-in URL with your 12 testers
Common Godot build issues and fixes
Export fails with "No Android SDK"
Fix: Install Android SDK via Android Studio and set the path in Godot Editor Settings
Permissions not granted at runtime
Fix: Godot 4+ requires runtime permission requests. Use the Engine.request_permission() method.
APK expansion files needed
Fix: Godot projects with large .pck files need Play Asset Delivery. Split into smaller scenes if possible.
How Expo developers get 12 testers for Google Play
Build command
eas build --platform androidPro tip
EAS handles signing automatically for managed workflows. For bare workflows, configure your keystore in credentials.json.
Play Console setup steps
- 1.Install EAS CLI: npm install -g eas-cli
- 2.Run eas build --platform android and follow the prompts
- 3.EAS builds your AAB in the cloud and provides a download link
- 4.Upload the AAB to Play Console → Testing → Closed Testing
- 5.Copy and share the opt-in URL
Common Expo build issues and fixes
EAS build queue is slow on free tier
Fix: Upgrade to a paid plan or build locally with npx expo run:android --variant=release
Native module not found in release build
Fix: Run npx expo prebuild --clean before building to regenerate native projects
App crashes on API 24-27 devices
Fix: Test on multiple API levels. Check your app.json for minSdkVersion and supported architectures.
How Ionic / Capacitor developers get 12 testers for Google Play
Build command
ionic capacitor build android --releasePro tip
Run npx cap sync before every build to ensure web assets and native plugins are up to date.
Play Console setup steps
- 1.Run ionic capacitor build android to prepare the Android project
- 2.Open the android/ folder in Android Studio
- 3.Build → Generate Signed Bundle → Android App Bundle
- 4.Upload AAB to Play Console → Testing → Closed Testing
- 5.Share the opt-in URL with testers
Common Ionic / Capacitor build issues and fixes
WebView not loading on some devices
Fix: Ensure AndroidSystemWebView is up to date. Test on devices with different WebView implementations.
Capacitor plugins missing in release
Fix: Run npx cap sync after installing plugins. Check android/capacitor.settings.gradle includes all plugins.
CORS errors in WebView
Fix: Configure your server with proper CORS headers. For local assets, use capacitor://localhost scheme.
After the build: getting your 12 testers
Once your AAB is uploaded and your Closed Testing track is live, you need 12 real testers who will actively use your app for 14 consecutive days — regardless of which framework you built with.
The opt-in URL from your Play Console tester tab is all you need. Share it with your testers, and they join your closed test with a single tap.
TesterBee matches your app with 12 verified testers on real Android devices within 24 hours, monitors their engagement daily, and guarantees the full 14 days — with a refund if production access is rejected due to tester issues.