Closed testing by framework
Flutter, React Native and Expo, FlutterFlow and AI-built apps: target API, building the AAB and the traps of each stack.
Google Play closed testing for Flutter apps
Ship a Flutter app through Google Play's 12-tester closed test: signed AAB, target API 36, version codes, permissions and the traps testers hit.
Google Play closed testing for React Native and Expo apps
React Native CLI or Expo EAS: build the AAB, target API 36, sign, bump version codes and avoid the internal-track trap before your 12-tester closed test.
Google Play closed testing for FlutterFlow apps
FlutterFlow deploys to Internal, then Production. The 12-tester rule needs a closed test in between. Here is the path, the keystore and the common errors.
Publishing an AI-built app on Google Play
Your AI builder made the app. Google still needs a signed AAB, API 36, a privacy policy and a 14-day closed test. Find what you have and what breaks.
Google Play closed testing for Unity games
Ship a Unity game through Google Play's 12-tester closed test: Unity versions for API 36, AAB, IL2CPP and ARM64, keystore, asset packs and permissions.
Google Play closed testing for Godot games
Ship a Godot game through Google Play's 12-tester closed test: Gradle build, AAB, target SDK 36 by version, keystore, version code and permissions.
Google Play closed testing for Capacitor and Ionic apps
Ship a Capacitor or Ionic app through Google Play's 12-tester closed test: Capacitor 8 for API 36, android/, cap sync, a signed AAB, version codes.
Google Play closed testing for Kotlin and Kotlin Multiplatform apps
Native Kotlin or Compose Multiplatform: target API 36 with the right AGP, build a signed AAB, bump versionCode and test R8 before the closed test.