Production access refused: “more testing needed”

What you see

Google answers your production access application: your app needs more testing before it can go to production.

Why

Google gives two kinds of reasons: fewer than 12 opted-in testers, or too little tester activity during the test. The decision belongs to Google alone, and Peerbeta can't change it.

What to do

1. Read Google's message and keep a screenshot of it.
2. Don't pause your closed testing track: keep the test going.
3. Pro and Launch: if the refusal is about testing and you applied within 7 days after the eligibility date, open the “Guarantee” section of your test, add the screenshot and the day you applied, then click “Claim the guarantee”. You get a free priority relaunch of 14 days, and a refund if Google refuses again. One guarantee per app.
4. Express: the relaunch covers a test that ended with fewer than 12 active testers, not Google's decision.
5. Before you apply again, fix what testers reported and announce each update to them.

What Peerbeta does

When a test is marked refused, the diagnosis raises it. Your report gives the active days of each tester and what you changed, which helps you answer Google's questions next time.