You finished the app. You paid the $25 for a Google Play developer account. You uploaded the build. And then Play Console told you production is locked until 12 testers stay opted in to a closed test for 14 continuous days.
Most solo developers hit this wall the day they think they're done, and most of them fail the first attempt: not because the rule is hard, but because the clock has rules nobody told them about. This is the plan I give people so they pass once.
The rule, precisely
Developers with personal accounts created after November 13, 2023 must run a closed test with at least 12 testers who have been opted in continuously for at least 14 days. Google originally required 20 testers and reduced it to 12 on December 11, 2024.
Three details that fail people:
- Continuous means continuous. A tester who opts in, tests for fewer than 14 days, and opts out doesn't count. If they opt out and back in, the 14 days restart.
- All 12 have to overlap. The 14-day window starts when the twelfth tester is opted in, not when the first one is.
- Passing the numbers isn't approval. When you apply, Google asks questions about your test, and reviewers can reject applications for insufficient testing engagement.
Organization accounts (registered with a D-U-N-S number) are exempt. For a solo developer, though, forming a company just to avoid testing costs more time and money than the test itself.
Why 12 is the wrong number to aim for
Testers get busy. Someone opts out on day 9 to free up storage. Someone's phone breaks. If you recruit exactly 12, one dropout resets everything.
Recruit 18 to 20. Tell every one of them, explicitly: stay opted in for the full 14 days, even if you stop using the app. That sentence prevents more failures than anything else in this article.
The 21-day plan
Day 0: Set up the track.
In Play Console → Testing → Closed testing, create a track, upload your AAB, and fill in the store listing, content rating, Data Safety form, and privacy policy URL. Google won't publish a closed-test release with an incomplete listing, and every day you spend fixing that is a day the clock isn't running.
Days 0–3: Recruit 18–20 real people.
The best sources, in order:
- Friends, family, coworkers with Android phones
- Your existing audience: newsletter, Discord, LinkedIn, a "help me launch" post
- Communities built for this: r/AndroidClosedTesting and similar tester-swap groups where developers test each other's apps
Collect their Google account emails. Add them to the tester list on the track, or create a Google Group and add the group.
Day 3: Confirm all 12+ are opted in.
Send the opt-in link. Then check the track's tester count in Play Console. The 14-day clock starts when the twelfth person is in, so don't assume; verify.
Days 3–17: Keep them engaged.
Google looks at engagement, not just enrollment. Ship at least one update during the window (a real one: a fix or a small feature) so testers have a reason to open the app. Send a short message on day 1, day 7, and day 13: "Thanks, please stay opted in until [date]."
Day 17: Apply for production access.
Play Console shows an "Apply for production" button once the requirement is met. The application asks how you recruited testers, what feedback you got, and what you changed. Answer honestly and specifically: "12 friends and 6 members of a tester community; feedback on onboarding copy and a crash on Android 12; fixed both in build 1.0.3." Vague answers get rejected.
Days 17–21: Wait for review.
Approval usually takes a few days. Once granted, you can release to production and use open testing for future betas.
What not to do
- Don't buy fake testers. Emulators, bot accounts, and "12 testers for $10" services risk permanent account suspension, and you lose the $25, the app, and the ability to open a new account.
- Don't start the clock before your listing is complete. A rejected closed-test release doesn't count toward anything.
- Don't assume a second app skips this. Play Console shows the requirement per app for affected accounts; plan for it every time until you see otherwise in your console.
- Don't recruit exactly 12. See above.
The pre-flight checklist
- [ ] Personal account created after Nov 13, 2023? (If yes, this applies.)
- [ ] Store listing, content rating, Data Safety, and privacy policy complete
- [ ] AAB uploaded to a closed testing track
- [ ] 18–20 testers recruited with Google account emails
- [ ] All testers told: stay opted in for 14 days
- [ ] Tester count in Console ≥ 12 before you start counting days
- [ ] At least one update shipped during the window
- [ ] Specific answers drafted for the production access application
If you'd rather not run this yourself
The 14 days can't be shortened, but everything around them can be handled: the listing, the Data Safety form, the track setup, the tester coordination, and the application. That's what LetsDeployIt does for AI-built and indie apps: done-for-you App Store and Google Play submission, including the closed-testing gate.
If you've been through this already: what got your testers to stay opted in for the full two weeks? I've seen everything from pizza to a shared leaderboard, and I'm curious what actually worked.
Top comments (0)