12 Testers for React Native: Google Play Closed Testing Guide

React Native apps on Google Play follow the exact same rules as native Android apps. Since November 2023, Google requires all new personal developer accounts to complete a Closed Testing track with at least 12 real testers engaged for 14 consecutive days before granting production access.

Whether you are using bare React Native or Expo with EAS Build, your app must go through this gate. Google does not distinguish between frameworks — it only looks at the AAB you upload and whether your testers show genuine engagement.

Yes, if your Play Console account is a personal developer account created after November 13, 2023. This covers most React Native developers — solo founders, indie devs, and startup teams using personal accounts.

No, if you have an organization account with a D-U-N-S number, or if your personal account was created before November 2023 and has already passed production access for a previous app.

Many React Native developers are surprised to discover this requirement only after building their app. The requirement applies when you apply for production access — not when you create your developer account — so you may not discover it until weeks or months into development.

For bare React Native (Android Studio):

For Expo with EAS Build:

For Expo projects, you will also need to configure eas.json with your keystore credentials or let EAS manage signing for you. Make sure your app.json includes the proper android.package and android.versionCode fields.

After uploading your AAB to Play Console, the Closed Testing setup process is identical regardless of framework:

1. Navigate to Testing → Closed Testing in Play Console
2. Create a new track and upload your signed AAB
3. Complete the store listing — app name, description, icon (512×512), feature graphic (1024×500), at least 2 screenshots, privacy policy, and content rating
4. Create an email list or Google Group with your testers' Gmail addresses
5. Share the opt-in link with your testers — they must click and accept
6. Start the rollout once testers are added

One extra step for React Native: make sure your app's AndroidManifest.xml includes the INTERNET permission if your app talks to any API. React Native apps commonly miss this and fail silently during testing.

The React Native community has active forums where you can find testers. Post in r/reactnative (130K+ members), the React Native Discord, and React Native Facebook groups. Offer to test other developers' apps in return — the React Native ecosystem has a strong culture of mutual support.

For guaranteed results, TesterBee provides 12 verified testers who actively use your React Native app for 14 days on real Android devices. Testing begins within 24 hours, with full engagement monitoring and dropout replacement.

Google tracks Daily Active Users (DAU), session duration, and device fingerprints throughout the 14 days. Push at least one update during testing — this shows Google you are iterating based on feedback. For React Native apps, even a minor UI tweak or dependency update counts. Use CodePush or EAS Update for over-the-air updates if you are using Expo.

React Native-specific monitoring:

• Watch for JavaScript bundle crashes — these appear in the Play Console under Android Vitals → ANRs & Crashes
• If using Hermes, verify the engine is enabled in your release build
• Test on both new and old Android versions — React Native's JS engine behavior can vary across API levels

After 14 days, apply for production access and answer the 6-question form. Each answer must be under 290 characters. Google wants to know: who your testers were, how they used the app, what feedback you received, what changes you made, and why the app is ready for production. Be specific — mention actual tester comments and the features you improved.

Most React Native developers receive a response within 3-7 days. Approvals typically come faster when engagement data shows consistent daily usage and at least one mid-testing update was published.

TesterBee provides 12 real testers on physical Android devices who test your React Native app daily for 14 days. You get engagement monitoring, dropout replacement, bug reports, device compatibility notes, and production access questionnaire support — everything you need to pass on your first attempt. Or earn free testing by testing other developers' apps.