12 Testers for Expo: Google Play Closed Testing Guide

Expo dramatically simplifies React Native development — and with EAS Build, getting an AAB for Google Play is just one command. But the Closed Testing requirement is the same: 12 real testers on real Android devices for 14 consecutive days. Expo's managed workflow adds some unique considerations around native module access, but the overall Play Console process is identical.

Configure eas.json with your keystore info or let EAS manage signing. In app.json, set android.package to your app's package name and android.versionCode to an integer. EAS handles the heavy lifting — native module compilation, signing, and AAB generation.

Upload your EAS-generated AAB to Play Console → Testing → Closed Testing. Complete the store listing, create a tester email list, share the opt-in URL, and start your rollout. The process is the same as any Android app — Google does not know or care that you used Expo.

The Expo community is active on r/expo, the Expo Discord, and the Expo forums. Expo developers are particularly receptive to tester exchange because they face the same publishing gate. TesterBee provides 12 verified testers for Expo apps — all on real Android devices with full 14-day engagement monitoring and production access support.

One advantage Expo gives you: EAS Update lets you push JavaScript-level changes to testers without going through Play Console review. Use this to fix bugs and add features during the 14-day period. Google still wants to see at least one Play Console-tracked update (an AAB upload), so combine EAS Updates for quick fixes with a mid-period AAB upload to show Google you are iterating.

After 14 days of active testing, apply for production access. In the questionnaire, mention that testers used your app on real devices and that you pushed over-the-air updates in response to feedback. Most Expo developers receive a decision within 3-5 days when engagement data is solid.