Troubleshooting

Production Access Shows Requirements Not Met

Why your Dashboard still shows testing requirements as unmet after weeks of closed testing, and what actually counts.

Reviewed August 17, 2026May change — always verify in Play Console1 official source

Written & maintained by AppsTestLabAbout AppsTestLabHow we research

On this page
  1. Why it happens
  2. The quick fix
  3. Step by step
  4. Things to check
  5. If this didn't work
  6. Common mistakes
  7. When to contact Google

The problem

You've been running a closed test for weeks, but Play Console still reports the production access requirements as not met.

Why it happens

The requirement is not about how long the test has run — it's about 12 or more testers being opted in continuously for at least 14 days. If testers opt out and in, stay below 12 for any stretch, or never complete the opt-in step, the continuous window resets or never starts.

The quick fix

Open your closed track's Testers tab, confirm 12+ verified accounts are opted in, and ask those testers to open your app at least once a day for the next 14 days without anyone opting out.

Step by step

  1. Count real opt-ins

    Invited is not opted in. Only testers who clicked the link and completed the opt-in step count toward the milestone.

  2. Check continuity

    A tester who opts out and back in starts their continuous period over. Keep the same 12+ people opted in for 14 straight days.

  3. Watch for engagement warnings

    Beyond the count, Google notes testing periods with insufficient tester engagement. Testers who open and use the app give you a stronger application.

Things to check

  • Live opted-in count today, not the count from two weeks ago
  • Whether any tester opted out during the last 14 days
  • Whether testers actually open and use the app (engagement)

If this didn't work

  • Recruit more testers than the minimum so one opt-out can't break your window.
  • Complete a full 14-day stretch with zero opt-outs before applying.

Common mistakes

  • Applying while counting testers who never completed opt-in
  • Testing in a track other than closed testing — internal tests don't count
  • Letting the count dip below 12 during the window

When to contact Google

If you believe your test genuinely meets the criteria and the Dashboard still blocks you, contact Play Console support via Help & feedback with your track details and dates.

Sources & references

Official Google documentation

These links open Google's official Play Console Help pages used to verify this guide. AppsTestLab guidance is independent and not affiliated with Google.

Last reviewed August 17, 2026 · Google Play requirements change — verify in the Play Console.

Ready to test?

5,000+ apps tested. A 99% historical approval rate. And a 100% money-back guarantee.

Tell us about your app and we'll confirm the right testing approach. One WhatsApp message to start, no complicated setup.

Guarantee applies to eligible app testing orders · Google makes the final approval decision

Chat on WhatsApp