Skip to content

Production access

Production access rejected? Here's what it means.

After a closed test, Google may decide your app needs more testing before it can go to production. The decision usually comes down to a few causes. Find yours, fix it and apply again with a stronger test behind you.

Find your reason

What Google officially says

Summarised from the Play Console Help page on app testing requirements. Google doesn't publish the exact wording of its decision emails, so the reasons on these pages are grouped the way developers report them.

  1. Personal developer accounts created after November 13, 2023 must run a closed test with at least 12 testers who have been opted in continuously for at least 14 days.

  2. You apply from the Play Console Dashboard with Apply for production. The form has three parts: about your closed test, about your app or game, and about your production readiness.

  3. Google says the review usually takes 7 days or less, but can occasionally take longer.

  4. If your app needs more testing, you may need to keep running your closed test. Google names fewer than 12 opted-in testers or insufficient tester engagement during the testing period as reasons.

Draft your application answers

A free, private helper that walks you through Google's three sections and turns your notes into well-structured drafts. Nothing leaves your browser.

Open the free helper

See what a well-documented test looks like

Daily participation, devices, scenarios, bugs and feedback, in the same report a TestBunny campaign produces. Demo data from a fictional app.

See a sample report

Run a closed test that holds up.

Real testers, every day on record, first testers within 6 hours of recruiting. If Google still says no after a completed campaign, you get one free re-test (claim within 30 days of completion).

TestBunny isn't affiliated with Google. Testers earn credits, never cash. Google alone decides on production access: nobody can guarantee approval, and we don't.