The rule
If your Google Play developer account is a personal account created on or after 13 November 2023, you cannot publish an app to production until you have run a closed test with at least 12 testers opted in continuously for 14 days. Once you meet it, the production access application appears on your Play Console dashboard.
Who it applies to
- Personal accounts created on or after 13 November 2023: the rule applies.
- Personal accounts created before that date: exempt.
- Organisation (business) accounts: exempt, whenever they were created.
- Apps that already have production access: exempt for all future updates. You do this once per app, not once per release.
How the number got to 12
Google introduced mandatory closed testing in November 2023 with a threshold of 20 testers. Developers found twenty people impossible to source and hold, and in December 2024 Google reduced it to 12. The 14-day window did not change, and has not changed since.
When the clock actually starts
Not when you create the track. Not when you upload the build. The 14 days are counted from the moment your twelfth tester opts in. Every day before that is setup, and none of it counts.
This is why a test that “took three weeks” often only banked ten days. If your twelfth tester joined on day four, day four was day zero.
The 14 days Google counts
Every one of these days needs 12 or more testers opted in. A single day below 12 resets the strip to empty.
Why it silently restarts
Continuously is the load-bearing word. If your count drops to 11 on day nine because someone got a new phone, cleared their app list or opted out without telling you, the continuous period is broken and starts again from the next day you are back at 12.
Play Console does not notify you when this happens. There is no email, no banner, no warning. Most developers discover it on day 14 when the production access application does not appear.
The defence is simple and almost nobody uses it: run with more than 12. Two or three spare testers absorb ordinary drop-off and the clock never breaks.
It must be closed testing
Internal testing does not count. Nor does open testing. Only the closed track satisfies the requirement, and this is the second most common reason a run produces nothing. The differences between the three tracks are worth two minutes before you start.
Testers have to actually use the app
Since 2026, Google assesses tester engagement separately from the count. Twelve accounts that opted in and never opened the app is a visible pattern, and the outcome is a request for more testing rather than a grant of access. Opting in is the floor, not the finish line.
How to get your 12
Four routes work, in rough order of effort:
- People you know. Free. Expect about half of those who agree to complete the opt-in without a reminder.
- Tester-swap communities. Free. You test other people’s apps for 14 days in return.
- Your existing audience. Free and the highest quality, if you have one.
- A paid testing service. Fast, and explicitly permitted: Google’s own production access questionnaire lists paid services as a recruitment channel.
The free routes, assessed honestly, including what each actually costs you in time.
Is paying for testers allowed?
Yes. Google’s requirement is that testers are real people on real devices genuinely using your app. How you found them is not the test. The questionnaire asks the question directly, and paid services are a listed answer. What is not allowed is fake accounts, emulator farms or installs that never open the app.
After the 14 days
The production access application appears on your dashboard. It asks how you recruited testers, what feedback you received, what you changed and how you decided the app was ready. Answer it specifically. A completed test with a vague application still gets refused.
If you were already refused
You do not need a new account, a new app or a new package name. You restart the 14 days on the same closed track. What to check before you re-run.