Google Play Production Access Denied: What to Do Next

What this rejection means

Your request for production access after the 12-tester closed test was turned down. Usually testers barely used the app, fewer than 12 stayed opted in for the 14 days, or the answers in the request were thin.

Why reviewers send it

New personal developer accounts must show a real closed test before publishing: 12 or more testers opted in for 14 days, actually using the app. Google reads the answers in the request; thin answers or a test nobody used are refused.

The message Google Play sends

Your app requires more testing to be granted production access.

We reviewed your application for production access and found that your app needs more testing before it can be published on Google Play. Continue testing with your closed test testers.

The exact wording changes from one review to the next; the policy name is what to look for.

How to fix it

Keep the closed test running: 12 or more testers opted in for 14 days in a row, actually opening the app.
Ship updates during the test that respond to feedback. New builds on the closed track don’t reset the clock.
Collect feedback in writing — a form or a group — so you can quote it.
Apply again with specific answers: what testers did, what they said, and what you changed.

The 12-tester countdown tracks the 14 days and drafts the answers for your next request.

What to tell Google Play

Replace the [brackets] with what you actually changed:

Our closed test ran with [n] testers for [n] days. They [what they did]. Based on their feedback we [changes], shipped in versions [x] and [y].

Got a different message?

Paste the whole rejection into the rejection explainer. It recognises this one and 26 others, in your browser — nothing is uploaded.

Google Play production access refused