FourteenYou kept 12 testers opted in for 14 days, filled in the form, and waited a week. Then Google asked you to keep testing. It's frustrating, and it's common. Google's review usually takes seven days or less, so another round costs you at least two more weeks.
Google doesn't publish a full checklist of rejection reasons, but its help page names two reasons for more testing, and developers report a few more patterns. Here's what to check before you apply.
1. Fewer than 12 testers stayed opted in
This is the first reason Google names. The count that matters is testers who stayed opted in continuously for the full 14 days. Anyone who left early, or opted out and back in, doesn't count for the full period.
Avoid it: recruit 15–20 testers from day 1, check the tester count in Play Console every few days, and ask testers not to leave until you say you're done.
2. Testers weren't engaged
This is the other reason Google names, and it catches more people. Twelve people who opted in once and never opened the app don't show Google your app was really tested. The application asks whether testers used all your features, and whether their use matched how real users would behave.
Avoid it: give testers a short task each day, like "create an event and set a reminder", so different features get used across the 14 days. Ask for a sentence of feedback after each one.
3. Your answers were vague
"Testers liked it and we fixed some bugs" doesn't say much. Answers that name the features testers used, the problems they found, and what you changed are much easier to believe.
Avoid it: keep notes during the test, not afterward. See how to answer the production access questions.
4. Nothing changed during the test
Part 3 of the application asks what you changed based on the closed test. If you never shipped an update, there's little to say, and the test can look like a formality.
Avoid it: fix a few things testers report, ship an update to your closed track during the test, and tell testers what changed.
5. Reviewers couldn't get into your app
Google's help page warns that review "is not a troubleshooting step." If your app needs a login, reviewers need working sign-in details in Play Console. Expired passwords, two-step verification, or features that only work with invited users can all block review.
Avoid it: create a dedicated review account, turn off two-step verification on it, and test signing in with it on a fresh device before you apply.
6. Policy problems in the app or listing
Production access is still a policy review. A missing privacy policy, a Data safety form that doesn't match what the app collects, or misleading store text can all cause rejections and delays.
Avoid it: check that your privacy policy link works, your Data safety answers match your app and every SDK in it, and your listing doesn't promise things the app doesn't do.
If you're asked to keep testing
- Keep your current testers opted in. Don't restart the whole test.
- Fix whatever is weakest: add testers if your count dropped, or add daily tasks if engagement was low.
- Collect specific feedback and ship an update, so your next answers have more to say.
- Apply again once you have a stronger, true story to tell.
I built Fourteen around these problems. Groups of 16 Android developers test each other's apps daily, with short tasks and an optional SDK that confirms real use, and it drafts your answers to Google from your test data. The first cohort begins Saturday, November 14, 2026.
More guides: How to get 12 testers · Why production access gets rejected · How to answer the production access questions
Fourteen is an independent project and isn't affiliated with or endorsed by Google. Google's rules can change, so check Google's help page for the latest. Questions? Email hello@getfourteen.app.