AppReviewX Log in

Production access not granted: what to do next

If the review asks you to continue testing, how to extend the test, add testers and apply again.

updated ·2 min read

In this guide

You applied for production access and the answer was no, or "continue testing". It is frustrating, but there are steps you can take. Google's help page says you may need to keep running your closed test if testing was insufficient, for example with fewer than 12 opted-in testers or insufficient tester engagement. It does not state a waiting period before you can apply again, so check the current help in Play Console.

Step 1: Read the message exactly

Open the notice in Play Console and copy the text. Note what it asks for: more testing, more testers, a clearer description, or something else. Do not guess what it means; act on what it says.

Step 2: Find the likely gap

Compare your test with the requirements. Check the current Play Console help for the exact numbers and rules.

  • Testers. Did you have enough testers opted in through the whole period? Did some leave? See what counts as 14 days.
  • Activity. Did testers actually use the app, or only install it?
  • Feedback and changes. Can you show what you learned and changed?
  • Answers in the form. Were they specific, or generic?

Step 3: Recovery checklist

  • [ ] Message copied and saved
  • [ ] Gap identified (testers, time, activity, answers)
  • [ ] Closed test kept running; do not stop it
  • [ ] More testers added, with a buffer for people who drop out
  • [ ] Testers asked for real use and structured feedback
  • [ ] Change log updated with every fix
  • [ ] Answers rewritten with specifics
  • [ ] Waiting period before re-applying checked in the current help

Step 4: Extend the test

If you are told to keep testing, keep the existing test going and add testers. Ask them to use the main flows and report what they find. Small, comparable feedback is easier to act on than loose comments, see beta feedback form.

Step 5: Apply again with a better story

Use your change log. Describe what you learned in the extended period, what you fixed, and why you now consider the app ready, see production readiness answers. Do not copy the previous answers.

What not to do

  • Do not ask for or offer reviews, ratings or installs in return for testing. AppReviewX does not do this.
  • Do not invent activity. Say what happened.
  • Do not delete the closed test.

AppReviewX offers test rounds for Google Play's closed-test requirement (12 testers, 14 days in a row, Android apps) and private, structured feedback. New accounts start with 0 credits; one feedback you write earns one credit. No result is guaranteed. Join a test round.

General information, not legal advice. Policies change.