Google Play closed testing
Production access rejected after closed testing: what to do
Short answer: keep your closed test running, get at least 12 testers using the app on several days, ship an update that acts on their feedback, and apply again with specific answers. LaunchReady keeps that engagement going free by swapping daily tests with other developers.
After your closed test, you apply for production access from the Play Console dashboard. Google reviews the application, usually within seven days. If it decides your app needs more testing, you will need to keep running the closed test and apply again. A rejection is not a ban. It means the evidence was not strong enough yet.
What the application asks
The form has three parts. Thin answers here are a common reason to be asked for more testing.
- About your closed test: how easy it was to recruit testers, how they engaged with the app, and a summary of their feedback.
- About your app: who it is for, what value it gives, and how many installs you expect.
- About production readiness: what you changed based on the test, and how you decided the app is ready.
Common reasons Google asks for more testing
- Fewer than 12 testers stayed opted in for the full 14 consecutive days.
- Testers opted in but rarely or never used the app.
- No feedback was collected, or none of it led to changes.
- The application answers were short or generic.
What to do now
- Read the decision. Check the email and the Play Console dashboard for the reason given.
- Keep the closed test running. Do not remove testers or the track. Anyone who opts out and rejoins restarts their 14 days.
- Check your tester count. Make sure at least 12 testers are still opted in, and add a few spare.
- Get real use. Ask testers to open the app on several days and try the main features, not just install it.
- Collect feedback and act on it. Ship at least one update to the closed track that fixes or improves something testers reported.
- Apply again with specifics. Say how you recruited testers, what they reported, which version fixed what, and why you now think the app is ready.
What not to do
- Do not pay for fake installs or bot testers. They do not create real engagement.
- Do not buy or trade public Play Store reviews. That breaks Google Play policy.
How LaunchReady helps
LaunchReady is a tester swap where developers test each other’s closed tracks. Cohorts of up to 17 developers open each other’s apps every day for 17 days, and testers can send private written feedback through the app. That gives you daily use, a tester buffer, and real feedback to describe when you apply again.
Related guides
- Google Play closed testing: 12 testers for 14 days (checklist)
- 12 testers or 20 testers? What Google Play requires now
- How to set up a Google Group for closed testing
- A free alternative to paid tester services
FAQ
Can I apply for production access again after a rejection?
Yes. Google may ask you to keep running your closed test first. Fix what the decision points to, keep testers active, and apply again from the Play Console dashboard.
Should I stop my closed test after a rejection?
No. Keep it running and keep testers opted in. A tester who opts out and rejoins starts their 14 days again.
How long does the production access review take?
Google says it usually takes seven days or less, but it can take longer.