If you created a personal developer account on Google Play after November 13, 2023, you can't publish your app straight to production. First you need to run a closed test with at least 12 testers who stay opted in for at least 14 days in a row. Until then, the Production track (and pre-registration) stay locked in Play Console.
Here is what the rule means in practice, based on Google's own help page.
What counts as a tester
A tester counts when they have opted in to your closed test with their Google account. Google is strict about the 14 days:
- Testers who opt in, test for fewer than 14 days and then opt out don't count.
- If a tester opts out and later opts back in, their 14 days have to be consecutive to count.
- When you apply for production access, at least 12 testers have to be opted in.
In other words: twelve people who join and leave again won't do. You need twelve people who stay.
It has to be a closed test
Play Console has three testing tracks: internal, closed and open. Only a closed test meets the requirement. Internal testing is a good place to start (it has no requirements and reaches testers within minutes), but it doesn't unlock production. Open testing needs production access itself. Read more about the difference.
You add testers to a closed test with email lists or Google Groups. With a Google Group, members join the group first and then opt in to the test through its opt-in link. The first time you publish a closed test, it can take several hours before the opt-in link works.
A timeline that works
- Day 0: set up the closed test, upload a release and send it for review.
- Day 0–2: when the release is available, get your testers in. The 14 days run for each tester from when they opted in, so the sooner twelve are in, the sooner you're done.
- Day 2–16: keep the testers in, and keep a release available to them. Collect their feedback as you go.
- Day 16: apply for production access from the Dashboard in Play Console (how to answer the questions). Google usually answers within seven days.
Plan for about three weeks from start to approval, more if testers drop out and have to be replaced: a new tester's 14 days start when they join.
Opted in isn't enough on its own
When you apply, Google asks how your testers used the app and what feedback they gave. If you had fewer than 12 opted-in testers, or the testers weren't engaged enough, Google can ask you to keep testing. So the testers should actually use the app during the 14 days, not just install it. Here is how to avoid that answer.
Where to find twelve testers
Google suggests your personal and professional networks and communities where your users gather, and recommends a group that reflects your audience. Friends and family can work, but keeping twelve of them active for two weeks is harder than it sounds. That's what Beta Family's testers are for.
Need the testers? Beta Family gives you 15 real testers who stay in your closed test for 14 days, write reports, and are replaced if anyone leaves. See the Google Play Production Pass.
More guides to Google Play testing
- How to answer Google Play's production access questionsAfter 14 days of closed testing, Google Play asks three sets of questions before production access. What it asks, and how to answer each part well.
- Why Google Play asks for more testing, and how to avoid itGoogle Play can ask for more testing when testers weren't engaged enough or fewer than 12 stayed opted in. How to keep your testers active for all 14 days.
- Closed testing vs internal testing on Google PlayInternal, closed or open testing on Google Play? How the three test tracks differ, and why only a closed test unlocks production for new accounts.