Building a React Native app for Android and trying to get it on Google Play? The mandatory closed testing requirement applies regardless of your framework. Here's the React Native-specific build process and how to navigate the 12-tester, 14-day requirement as quickly as possible.
React Native Build Options for Google Play
You have two main options: Expo managed workflow or bare React Native. The build process differs slightly.
Option A: Expo (Managed Workflow)
If you're using Expo, building an AAB for Google Play is straightforward:
eas build --platform android --profile productionRequires EAS CLI (
npm install -g eas-cli) and an Expo account. EAS Build handles signing automatically if configured.In your eas.json:
{"build": {"production": {"android": {"buildType": "app-bundle"}}}}Option B: Bare React Native
For bare React Native projects, build via Gradle:
cd android && ./gradlew bundleReleaseOutput:
android/app/build/outputs/bundle/release/app-release.aabYou need a keystore configured in android/gradle.properties:
MYAPP_UPLOAD_STORE_FILE=release-key.keystore
MYAPP_UPLOAD_KEY_ALIAS=release-key-alias
MYAPP_UPLOAD_STORE_PASSWORD=your_password
MYAPP_UPLOAD_KEY_PASSWORD=your_passwordUploading to Google Play Closed Testing
- Go to Google Play Console → Testing → Closed Testing
- Create a track or use the default "Alpha" track
- Upload your
app-release.aab - Complete release notes and roll out
- Wait for Google's track review (typically a few hours)
- Once published, copy the opt-in URL from the Testers tab
Common React Native Play Store Issues
Hermes engine compatibility
If you're using Hermes (enabled by default in React Native 0.70+), make sure your Gradle build configuration supports it. Most modern React Native setups handle this automatically, but if you're on an older version, check the Hermes documentation for your RN version.
64-bit requirement
Google Play requires apps to support 64-bit architecture. React Native apps do this automatically in recent versions. If you're on an older version and getting rejection messages about 64-bit support, upgrade React Native or check your abiFilters in build.gradle.
Large bundle size
React Native apps tend to have larger bundle sizes. Enable ProGuard in release builds and use the AAB format (which automatically splits the APK by device configuration, reducing download size for users).
The Closed Testing Requirement for React Native Developers
The framework you used doesn't change Google's requirement: 12 real Android users opted in for 14 consecutive days. The React Native community has active spaces for tester swaps (r/reactnative, various Discord servers), but the reliability issues are universal — strangers don't stay committed for 14 days.
{CTA}React Native App Publishing Checklist
- ☐ Keystore generated and backed up securely
- ☐ Release build tested on a physical Android device
- ☐ Hermes enabled (React Native 0.70+)
- ☐ ProGuard/R8 enabled for release builds
- ☐ Privacy policy URL live and accessible
- ☐ Data Safety form completed in Play Console
- ☐ Screenshots taken on a real Android device
- ☐ Closed testing track published
- ☐ 12+ testers opted in via official opt-in URL
- ☐ 14 consecutive days with 12+ testers
- ☐ Production access form submitted
How Fast Can You Get a React Native App Live?
With everything in order and TestLaunch Pro handling testers:
- Build + upload to closed testing: 1 day
- Testers opted in: 6 hours after ordering
- 14-day testing period: 14-16 days
- Production access review: 3-7 days
- Total: approximately 20-25 days from first build to live on Google Play