On this page
The problem
You applied for production access, but the Dashboard shows the application was not approved, was returned, or asks for continued testing.
Why it happens
Approval comes after an actual review of your test. The usual reasons: fewer than 12 testers were opted in continuously for the required period, tester engagement was too low during the window, or the answers in your application didn't match what Google could see in its review of your app — for example, describing features or test usage that the review found no evidence of.
The quick fix
Open the feedback on the Production access page in Play Console, read the specific reason named there, and address exactly that gap before doing anything else — then rebuild a full 14-day window before reapplying.
Step by step
Read the feedback first
Your Dashboard records why the application was not approved. Fix the named reason — not what you assume it was.
Identify the gap
Check the live opted-in count today. If testers dropped below 12 at any point during the 14 days before your application, or the window was never continuous, that alone explains the result.
Address engagement too
Google reviews the test period, and continued testing can be requested when engagement is low. Get your 12+ testers opening and using the app during the window, not just installing it once.
Rebuild the window
Run a fresh, continuous 14-day window with at least 12 testers opted in throughout — no opt-outs, real usage — before you reapply.
Reapply
Submit the production access application again, and make sure your answers describe exactly what your test shows: the track used, the test period, and the feedback you addressed.
Things to check
- The specific feedback recorded on the Production access page
- Live opted-in count at application time — not the count from week one
- Continuity: any opt-outs during the last 14 days
- Real engagement during the window
- Matches between your application answers and the app's actual state
If this didn't work
- Check that your app's policy standing is clean — a separate policy issue can surface here as a testing problem.
- If the feedback mentions app content or functionality, review the app against Google Play policies rather than re-running the test.
- Reach Play Console support when the feedback doesn't state a clear, actionable reason.
Common mistakes
- Reapplying without changing anything — the same application gets the same result
- Assuming 'not approved' is an account ban — it's a testing verdict, not a suspension
- Letting testers drop off during the review itself after applying
When to contact Google
Contact Play Console support if the feedback is unclear about what's needed, or you believe your test met the requirements exactly and the decision looks mistaken.
Sources & references
Official Google documentationThese links open Google's official Play Console Help pages used to verify this guide. AppsTestLab guidance is independent and not affiliated with Google.
Last reviewed August 17, 2026 · Google Play requirements change — verify in the Play Console.