Google denied production access after closed testing. What now?

You completed the testing period, applied, and Google asked for more testing. That’s a separate decision from whether your app passes policy review. Meeting the tester requirement lets you apply; it doesn’t guarantee production access.

Read the response alongside Google’s production-access application guidance. It asks about engagement, feedback, changes, and readiness. Start with the reason Google gave you, then check what your testing record can actually demonstrate.

Identify the stage that’s holding you up

What Play Console shows	Where to work next
You can’t apply yet	Check the continuous opt-in counter
More testing is required	Continue the closed test and address the application feedback
Production access is granted	Prepare the separate production release and app review
A production release is rejected	Follow the cited policy rejection

Keep the original response. It gives you a better starting point than guessing from someone else’s approval story.

Make the next test useful

We recommend giving testers a task they can finish and a simple place to report what happened. “Please test the app” leaves you with very little to learn from.

For a booking app, an example task might be finding an available appointment, booking it, changing it, and checking the confirmation. Choose tasks from your actual app, including sign-in, empty states, permissions, and paid access where relevant.

Use this blank record for each meaningful finding:

Field	What to write
Build and test date	Which version the person used
Task and device	What they attempted and on what device
Result	What worked or where they got stuck
Feedback	Their actual observation, with private details removed
Change	The fix or product decision you made
Retest	Whether the changed flow worked afterward

Recruit people who can use the app and respond when something breaks. Purchased opt-ins or a schedule of empty app launches won’t give you this evidence. Google doesn’t publish a universal daily-minutes or daily-open quota in this guidance.

Reapply with what changed

Check Play Console for the next eligible application step. Answer from your records: who tested, what they exercised, how you collected feedback, what you changed, and why the app is ready. If a test found no issue, say what you checked and what worked rather than inventing a bug and fix.

Keep the test available while you address Google’s response. Once access is granted, continue to the production submission steps; access approval itself doesn’t make the app public.