Google Play rejected your production access request? What to fix

The most common reasons a production access request is turned down after a closed test, and how to run the next test so it passes.

Updated 20 Nov 2026

First, read the email from Google

A rejection is not a ban. Google’s email says that your app needs more testing and usually points to the area that was not convincing: tester engagement, the feedback you collected or how ready the app looks. Start from there instead of guessing.

You can keep testing on the same closed track and apply again once you have better evidence.

Testers were not really engaged

Google looks at whether testers used the app, not only whether they were opted in. Twelve accounts that installed the app on day 1 and never opened it again look like a formality.

Give testers concrete tasks, ship an update halfway through and ask for written feedback at the end. On TesterTribe every tester gets a list of tasks from you and must leave a structured feedback report to close the test.

Testers did not stay for 14 days in a row

The requirement is 12 testers opted in continuously for the last 14 days. If a few testers opted out or were removed from your list, you may have dropped below 12 without noticing.

Check the tester list on the day you apply, and keep a couple of reserves. TesterTribe campaigns have 12 testers plus 2 reserves, and you can report anyone who leaves.

Vague answers in the application

Answers like “testers liked the app” do not tell the reviewer anything. Give numbers and examples: how many testers, how many feedback reports, which bugs were found and fixed, which release shipped the fixes. Our guide on the production access questions shows what to write for each one.

The app does not look ready

Crashes, placeholder screens, broken login or a store listing with missing screenshots make the app look unfinished. Fix the issues testers reported, test on more than one device and complete the store listing before you apply again.

Run the next test properly

Before you apply again:

  1. Fix the problems from the first test and ship a new release to the closed track.
  2. Make sure at least 12 testers have been opted in for the last 14 days, with reserves in case someone leaves.
  3. Give testers specific tasks and collect written feedback from each of them.
  4. Rewrite your answers with numbers, examples and the list of changes you made.

Frequently asked questions

Can I apply again after a rejection?

Yes. Keep testing, improve the app and your answers, and apply again from the Play Console dashboard.

Do I need a new closed test after a rejection?

You can keep using the same closed track. What matters is that at least 12 testers have been opted in for the last 14 days when you apply again.

Need 12 testers who stay? Join the tribe: your first campaign is free. Browse apps to test