Check these first
- The tester count in Play Console does not refresh instantly, so log it daily to see when dropout happened.
- The top cause of dropout is a failed first run (crash, cannot sign in). Check the first-run experience right after the test starts.
- Recruiting 3-5 above the requirement keeps the 14-day count from breaking when some testers leave.
- Testers recruited through an exchange drop out less because their own test depends on it. Prefer mutual exchange over anonymous recruiting.
Read alongside the official docs
Platform policy changes, so treat this page as a reference checklist and confirm the official documentation before your final submission.
Frequently asked questions
- Q. If a tester deletes the app midway, does the 14 days reset?
- Not entirely, but any period where retained testers fell below the requirement (12) may not count as continuous participation. Keeping spare testers so the required count always holds is the safer approach.
- Q. How do I check whether a tester installed?
- Play Console shows the tester count on the closed testing track, but not in real time. An exchange platform lets you track install confirmation per participant, so you spot dropout sooner.
- Q. Can I replace a tester who dropped out?
- Yes, you can add testers during the test window. Their participation days are counted from when they join, so the overall completion date may move later.
Post whatever is blocking you
Include your app name, platform, current launch stage, and the docs you already checked — it helps answerers narrow down the cause.