Who has to do this?
The rule applies to personal developer accounts created after November 13, 2023. Until you meet it, the Production track (and features like pre-registration) stay locked in Play Console. Organization accounts aren't covered by this testing rule, but they need a D-U-N-S number and extra business verification, which can take weeks. For most solo developers, the closed test is the faster route.
Google first asked for 20 testers. It lowered the number to 12 in late 2024, and that's the current number.
What the rule actually says
- It must be a closed test. Internal testing doesn't count.
- At least 12 testers must be opted in at the moment you apply for production access.
- Those testers must have been opted in continuously for the 14 days before you apply. It's a rolling window, not a one-time total.
- When you apply, Google asks questions about how you tested, what feedback you got, and whether your app is ready.
Step-by-step: from upload to production
Create a closed testing track
In Play Console, go to Test and release → Testing → Closed testing and create a track. Upload a signed release (AAB) and complete the basic store listing and app content forms so Google can review the build.
Add your testers
Add testers by email list or a Google Group. Every tester needs a Google account. Use people who will really install and open the app. Enthusiastic friends and fellow developers work better than a large list of strangers who never open it.
Share the opt-in link and confirm installs
Once the build is reviewed, Play Console gives you an opt-in link. Each tester opens it, taps Become a tester, then installs the app from Google Play. Sideloaded APKs don't count. Check the tester count in Play Console after a day or two.
Keep at least 12 opted in for 14 days in a row
This is where most developers get stuck. Testers lose interest, uninstall or opt out, and the count dips below 12. Aim for 15–20 testers, send a short reminder every few days, and give them something specific to try each week.
Collect feedback and ship an update
Ask testers to report bugs and ideas, then fix the important ones and publish at least one new version to the closed track. This gives you real answers for Google's questionnaire and shows the app improved during testing.
Apply for production access
After 14 continuous days with 12+ testers, the Apply for production button unlocks on the Dashboard. Answer the questions honestly and specifically: who tested, how you recruited them, what they found, and what you changed. Google's review can take several days, so plan for about a week.
Common mistakes that get applications refused
- Recruiting exactly 12. One drop-out restarts your wait. Always keep a buffer.
- Testers who never open the app. Opted-in but inactive testers make for a weak application.
- Using emulators, bots or your own extra accounts. Google is looking for real people on real devices.
- No changes during the test. Applying with the same build and no feedback suggests the test wasn't real.
- Vague questionnaire answers. "Friends tested it, no issues" is much weaker than specific bugs you found and fixed.
Where to find 12+ real testers
- Friends, family and colleagues with Android phones. They're the most reliable, but you need a lot of them.
- Developer communities such as Android developer subreddits and Discord or Telegram groups, where developers test each other's apps. Free, but people drop out often.
- A managed tester panel like TesterHive. Real testers with their own verified emails opt in through your official link, and a dashboard tracks the 14-day streak and warns you before the count dips.
Get your 12+ testers with TesterHive
Real opted-in testers, a live 14-day streak tracker with drop-out alerts, structured feedback with screenshots, and an export to help you answer Google's questions. Your campaign starts as soon as you pay, and every account gets 1 free AI test run.
- Testers use your official Play Console opt-in link
- Alert the moment you fall below 12
- Pay with UPI, cards, netbanking or PayPal
No service can guarantee Google's approval. TesterHive coordinates real testers and gives you the data. The production-access decision is Google's. TesterHive is not affiliated with or endorsed by Google. Rules can change, so always check Google's official Play Console Help page.
FAQ
Who has to meet the 12 testers / 14 days requirement?
Developers with a personal Google Play Console account created after November 13, 2023. Organization accounts are not covered by this requirement, but they need extra verification such as a D-U-N-S number.
What happens if a tester leaves during the 14 days?
Google looks at whether at least 12 testers have been opted in continuously for the 14 days before you apply. If your count drops below 12, you need to get back to 12 and keep them for another 14 continuous days before you're eligible. That's why it's smart to start with 15–20 testers.
Can I use emulators, bots or my own extra accounts?
Don't. Testers should be real people on real devices who install from Google Play and actually use the app. Google asks about your testing when you apply for production access, and fake or inactive testers are a common reason applications are refused.
Do testers need to install the app from Google Play?
Yes. They must opt in through your closed test's opt-in link, and then install the app from the Play Store. Sideloading an APK doesn't count as being in the test.
How long does production access review take?
Google doesn't promise a fixed time, and reviews can take several days or longer. Plan for about a week after you apply.
Does AI or automated testing count toward the 12 testers?
No. Only real, opted-in people count. Automated testing is still useful for catching bugs before your testers do, but it doesn't replace the closed test.