PeerTest

Fewer than 12 testers for 14 days

Google's help page lists this reason as “having fewer than 12 opted-in testers”. The rule it enforces is twelve testers opted in continuously for at least fourteen days.

Where the count goes wrong

What to do before applying again

  1. Recruit more than twelve. Some will leave; a margin of two or three keeps you above the line when they do.
  2. Start them together. Fortnights that begin the same week overlap for the whole test.
  3. Watch who is still opted in. Play Console shows the count. Check it every few days, not on day fourteen.
  4. Engagement still counts. Twelve who opted in and never opened the app is the other refusal, testers were not engaged.

What PeerTest does about it

Every other Monday is a launch cohort: developers who list an app and join start on the same day, so their testers' fortnights overlap from the first one. A seat is a fourteen-day commitment to one app, with a short check-in most days, and a tester who goes quiet for three days gives the seat back so it can be filled again.

It is not fast. From nothing, the twelfth tester usually finishes around day thirty, because testers are paid for in testing rather than money. The services promising twelve testers in six hours are selling the count, and the count is the half that was never the problem.

See what is open on PeerTest →

Google's words are quoted from its Play Console Help page “App testing requirements for new personal developer accounts”, at support.google.com/googleplay/android-developer/answer/14151465, as read on 22 October 2026. Google changes these pages; where this one disagrees with Google's, Google's is right.

PeerTest · Why production access is refused · Example report · Privacy · Terms · Your Privacy Choices