You applied for production access and the answer was not "approved". Google asked you to keep testing. That is frustrating, but it is not the end, and the message usually points to something you can fix. This guide goes through what Google says, what to check, and how to apply again with a better case.

The facts here come from Google's own help page. Read your own message from Google first, because it is about your app.

What Google says about more testing

Google states that if your app requires additional testing, you may need to continue running your closed test. It names two reasons:

1. Fewer than 12 opted-in testers.
2. Insufficient tester engagement during the testing period.

It also says review usually takes seven days or less but can occasionally take longer.

Step 1: Read the message, do not guess

Copy the full text of Google's message into a document. If it names a reason, work on that reason first. If it is general, go through the checks below.

Step 2: Check the number of testers

Open your closed test and count testers who were opted in continuously for the 14 days before you applied. Testers who opted out early, or who opted out and back in without a consecutive 14 days, do not count. If you were close to the limit, a single dropout may be the whole story. Our guide on what to do when a tester drops out explains how to count.

Step 3: Check engagement

"Engagement" is about whether testers really used your app. Ask yourself honestly:

• Did testers use the main features, or only open the app once?
• Did you collect feedback, and can you show it?
• Did your testers behave like the real users you expect?

If the honest answer is "not really", the fix is not a better paragraph. It is more real use. Give testers clear instructions, ask them to try specific features, and collect their notes. A feedback record makes this easy to show.

Step 4: Check policy and stability

Google says review is not a troubleshooting step. It tells you to check your app against its policies before applying, and it points to four common areas:

• App content and features, including monetization.
• Target age group and content rating, so that your store listing settings match your real audience.
• Functional reliability: no crashes, broken functions or missing screens.
• Test credentials: if your app needs a login, give valid, working login details in Play Console so reviewers can test it.

Test credentials that do not work are an easy mistake to make and an easy one to fix.

Step 5: Fix, keep testing, collect, then apply again

• Fix what you found, and note each fix.
• Keep the closed test running with enough testers, ideally with a buffer above 12.
• Keep collecting feedback.
• When you apply again, write new answers for the three parts of the form. Describe what you changed because of what testers found, and how you decided the app is ready. Do not paste the same text as before.

What not to do

• Do not buy fake installs or fake feedback. It breaks Google's rules and can put your account at risk.
• Do not rush a new application the same day with nothing changed.
• Do not stop collecting feedback after you apply.

If you used ClosedTest

Our refund policy covers this situation: if Google rejects your production access after our test, we offer a free re-run first, and a refund if that also fails. Conditions apply. For example, it does not cover cases where we reported real bugs and they were not fixed before you applied. The full rules are on the refund page.

If you used ClosedTest, send us what Google wrote and we will look at it with you.

ClosedTest is an independent service and is not affiliated with Google.