If you have a personal Google Play developer account created after 13 November 2023, you can't publish to production until you've run a closed test with at least 12 testers opted in for 14 days in a row. Then you apply for production access and answer Google's questions about the test.
A lot of solo devs get through the 14 days and still get the "your app requires more testing" email. I've seen the same handful of causes come up again and again in the Play Console community, so here they are with what actually fixes each one.
Disclosure: I run App Circle, a free test-for-test site for Android devs. I'll mention it once near the end; everything else applies whatever route you use.
1. The 14 days weren't continuous
Google counts testers who stayed opted in for 14 continuous days. If your count dipped to 11 on day 9 because someone left the Google Group or opted out, the clock effectively restarts.
Fix: recruit 15 to 20 testers, not exactly 12. Check the "Testers" count on the closed testing track every couple of days, and replace anyone who drops off early rather than on day 13.
2. Testers opted in but never actually used the app
The production-access form asks how testers engaged with your app. If Play Console shows almost no installs or sessions, "12 people joined" isn't enough.
Fix: ask testers to install from the opt-in link (not a sideloaded APK), open the app on several days, and try specific features. Give them a short checklist: "Day 1 sign up, day 3 try X, day 7 send feedback".
3. No evidence of feedback or changes
Google wants to see that the test improved the app. An app that shipped one build on day 1 and nothing after looks like the test was a box-ticking exercise.
Fix: collect feedback (a Google Form, the Play private feedback channel, or a group chat) and push at least one or two updated builds to the closed track during the 14 days. Mention those changes in your answers.
4. Vague answers on the application form
"Testers tested the app and it worked" is the classic rejection trigger. The form asks who your testers were, how you recruited them, what feedback you got and what you changed.
Fix: be specific and honest. Name the recruitment method, give numbers ("17 testers, 11 sent feedback"), list two or three concrete fixes, and explain why the app is ready for production.
5. Testers on work or new throwaway accounts
Testers need to opt in with a normal Google account on a real device. Batches of brand-new accounts, emulators or the same person on multiple accounts are exactly what the rule is designed to catch.
Fix: use real people on their personal Android phones. Avoid anyone selling "12 testers for $10" with suspiciously identical accounts; if Google sees it as inauthentic, you've lost 14 days and risk your account.
6. The app itself isn't production-ready
Crashes in Android vitals, placeholder content, a broken login, or a store listing that doesn't match the app can all cause a "more testing" response even if the tester numbers are fine.
Fix: check Android vitals for crashes and ANRs, make sure reviewers can get past any login (provide demo credentials in App content), and fill in every App content declaration.
7. Applying on day 14 exactly
Time zones and when each tester opted in mean "14 days" on your calendar may be 13.5 days by Google's count.
Fix: wait until the Dashboard shows the requirement is met, and give yourself a day of buffer before you apply.
Where to find testers without paying
- Friends and family with Android phones (send them the opt-in link and a reminder schedule).
- Facebook and Discord test-for-test groups: test others' apps and they test yours.
- Test-exchange sites. I built App Circle for this: devs test each other's apps for virtual coins (no money), and the companion app checks testers open your app daily, which helps with points 1 and 2. It's free, and of course it can't guarantee Google's decision.
If you got rejected, don't panic: fix what applies above, keep (or rebuild) your tester pool, run another 14 days, and write a more detailed application. Most apps get through on the second attempt.
Good luck with your launch!
Top comments (0)