You finished your Android app, opened Google Play Console to publish it, and found that the production button is locked. If you are using a new personal developer account, Google wants proof that real people have tested your app first.
Google Play requires new personal developer accounts (created after 13 November 2023) to run a closed test with at least 12 testers who have stayed opted in for at least the last 14 days continuously before they can apply for production access. Once that condition is met, you answer questions in Play Console about your test and your app, and Google reviews the application before you can publish publicly.
Who does the 12 testers requirement apply to?
The requirement applies to personal developer accounts created after 13 November 2023. When it was introduced the threshold was 20 testers, and Google later reduced it to 12. Organisation accounts, which are verified with business details such as a D-U-N-S number, are not subject to this closed testing requirement. If you are publishing for a registered company, it is worth considering whether an organisation account is the more appropriate choice from the start. Always check the current Play Console Help Centre, as Google does update these policies.
What exactly does Google check?
| Requirement | What it means in practice |
|---|---|
| Closed testing track | The test must run on a closed track, not internal testing or open testing |
| At least 12 testers | Twelve or more people must have accepted the invite and opted in |
| 14 continuous days | Those testers must have stayed opted in for at least the last 14 days without a break |
| Application for production | You answer questions about how you ran the test, the feedback, and your readiness |
| Review | Google reviews your answers and the app before granting production access |
How do you set up a closed test in Play Console?
- Prepare a release build. Upload a signed Android App Bundle (AAB) that targets the API level Google Play currently requires.
- Complete the app content sections. Fill in the privacy policy, data safety form, content rating, target audience and any other declarations Play Console asks for.
- Create a closed testing track. Under Testing, choose Closed testing and create a track (the default is often called "Alpha").
- Add testers. Add tester email addresses directly or, more conveniently, use a Google Group so people can join and you can manage the list in one place.
- Roll out the release to the track and wait for it to be reviewed.
- Share the opt-in link. Each tester must open the link, accept the invitation with the Google account you added, then install the app from Google Play.
How do you find 12 reliable testers?
The hardest part is usually not the setup but keeping a dozen people engaged for two weeks. Good sources include:
- Early customers or people who joined your waitlist during idea validation.
- Friends, colleagues and family who match your target audience and use an Android phone.
- Members of relevant professional or community groups who would genuinely benefit from the app.
- Your own team and the team of your development partner, as long as they test properly.
Recruit more than 12 people. Some will forget to opt in, use the wrong Google account or leave the test, and if your count drops below 12 the continuous 14 days may need to start again. Be cautious about paid "tester exchange" services: Google asks detailed questions about your testing, and an app tested by people with no real interest gives you nothing useful to report.
How do you make the 14 days count?
Google wants to see that you used the test to improve the app. Treat the two weeks as a genuine beta rather than a waiting period.
- Give testers a short list of tasks to try, such as signing up, completing the main flow and using key features.
- Collect feedback through a simple form, a WhatsApp or Telegram group, or the private feedback channel in Play.
- Monitor crashes with Firebase Crashlytics or Sentry, and check pre-launch reports in Play Console.
- Ship at least one updated build that fixes issues testers found, and keep a short record of what changed.
How do you answer the production access questions?
When the conditions are met, the "Apply for production" option becomes available on the Play Console dashboard. You will be asked about how you recruited testers, how engaged they were, what feedback you received and how you acted on it, and who your app is for. Answer honestly and specifically. Vague answers such as "testing went well" are more likely to lead to a rejection than concrete notes such as "testers found the sign-up confusing, so we simplified it to one screen in version 1.0.3".
If the application is rejected, Google usually asks you to continue testing. Keep your testers engaged, gather more feedback, make improvements and apply again.
Common reasons closed tests fail
- Testers were added to the list but never accepted the invite.
- The test ran on internal testing instead of closed testing.
- Testers left partway through, breaking the 14-day continuity.
- No updates were released during the test, suggesting little real testing happened.
- Answers to the production questions were generic.
Key takeaways
- New personal accounts need at least 12 opted-in testers on a closed track for 14 continuous days before applying for production.
- Recruit more than 12 real users and use the period to fix issues and ship updates.
- Give specific, honest answers about your testing when you apply for production access.
AppifyDevs manages Play Console setup, closed testing, release builds and store listings as part of our Android projects, so your launch is not held up by process. Get a quote for mobile app development, and once you are live, our guide to app store optimization will help people find your app.