Production access rejected? Here is what to check first
A rejection is almost always one of six causes. Work through them in order before you resubmit, because an identical application produces an identical answer.
Do not immediately resubmit
The instinct after a rejection is to send it straight back. Resist it. Nothing about the outcome changes unless something about the application changes, and repeated identical submissions do not help how your account is viewed.
The six usual causes
In rough order of how often they turn out to be the problem:
- Fewer than 12 testers actually opted in - invited is not opted in
- The 14 days were not consecutive, or the count dipped mid-window
- Tester activity clustered into the first day or two
- Form answers too thin to show the test informed the app
- Store listing, privacy policy or data safety incomplete
- Tester accounts that look synthetic to Google
Check the count that Google sees
Open Play Console and look at the opted-in tester count on the closed track, not your invite list. These two numbers are different, and the gap between them is the single most common cause of a failed requirement.
Rewrite the answers properly
If your test genuinely ran for fourteen days with twelve real testers, the rejection is usually about the form rather than the test. Go back with specific findings and specific changes. See our guide on answering the production access form for what each question is testing.
Then run a clean test
If the underlying test was flawed - too few testers, a broken streak, activity that stopped after day two - a rewrite will not save it. Run a clean fourteen days with margin above the minimum and apply again on the strength of that.