The 12 testers, 14 days rule: what Google's help says

Updated 2026-11-14 · Checked against Google's official help pages

If your personal developer account was created after November 13, 2023, each app needs a closed test with at least 12 testers who have stayed opted in for at least 14 days in a row before you can apply for production access. You also need 12 testers opted in on the day you apply. Internal testers don't count, and anyone who opts in to your internal test can no longer be in your closed test.

The rule, line by line

Item	What the help page says
Who	Personal Play Console accounts created after November 13, 2023
How many	At least 12 testers
How long	Opted in continuously for at least 14 days
When you apply	At least 12 testers still opted in to the closed test
Scope	Per app, not once per account
Track	Closed testing. Internal testing is optional. Open testing only unlocks after you get production access
Review	Usually seven days or less, occasionally longer

"At least 12 testers must be opted in to your closed test when you apply for production access."
— Play Console Help: App testing requirements for new personal developer accounts

One small wrinkle: the English page says accounts created "after" November 13, 2023, while the Japanese page says "on or after" (以降). If you created your account on that exact day, check whether Play Console shows the testing requirement on your dashboard.

When 20 became 12

Google announced the rule on the Android Developers Blog on November 9, 2023. At the time it asked for at least 20 testers over at least two weeks. An update dated December 11, 2024 on the same post lowered the number to 12 for personal developer accounts. The 14 days did not change.

Plenty of older tutorials, videos and forum answers still say 20. If what you're reading predates December 2024, assume the tester count is out of date.

It applies to every app

The help page says personal accounts "must run a closed test for their app". Read plainly, getting your first app into production does not exempt your second one. If friends helped you once, ask early whether they'd be willing to help again.

Only the closed track counts

In Google's table of testing tracks, the prerequisite for production is a closed test with 12 opted-in testers for 14 days. Internal testing is described as optional but a good starting point; nothing says internal testers count toward the 12. Open testing only becomes available after you have production access, so it can't be used to meet the rule.

The internal testing trap

This one catches people. A tester who opts in to your app's internal test drops out of eligibility for the closed test, even if their address is also on the closed test list.

"Users who opt into internal testing aren't eligible for open and closed testing, even if included as testers on those tracks."
— Play Console Help: Set up an open, closed, or internal test

If you invite a friend to the internal track for a quick smoke test, you may lose them as one of your 12. Keep internal testing to your own devices and to people you don't plan to count.

Not stated by Google: The help page never explicitly exempts organization accounts; it only says the rule covers personal accounts. It doesn't say whether someone who leaves the internal test becomes eligible for the closed test again. It doesn't say what happens if you dip below 12 testers partway through, and vendor blogs disagree with each other on this. It also doesn't say whether opt-ins from an iPhone or an emulator count.

Related guides

Sources

Play Console Help: App testing requirements for new personal developer accounts (checked 2026-11-14)
Play Console Help, Japanese version of the same page (checked 2026-11-14)
Play Console Help: Set up an open, closed, or internal test (checked 2026-11-14)
Android Developers Blog: Ensuring high-quality apps on Google Play (2023-11-09, updated 2024-12-11) (checked 2026-11-14)