Testers Not Showing in Play Console? 8 Things to Check
Your testers say they joined, but Play Console doesn't count them. Here's a checklist of the usual causes, from the wrong Google account to a track that isn't live.
The checklist
1. They didn't actually opt in
Opening the link isn't enough. Testers must tap Become a tester on the opt-in page. Ask them to open the link again. If they see "You are a tester", they're in.
2. They used a different Google account
Many people have more than one Google account. The one that opts in has to be the same account that's on your tester list and signed in to Play Store on their phone.
3. Their email isn't on your list
Check the Testers tab on your closed track. Is their exact Gmail address on the email list? Typos and old addresses are common. And make sure the list is actually ticked/enabled for that track.
4. They haven't accepted the Google Group invite
If you use a Google Group, a person who was invited but hasn't accepted isn't a member yet, so they can't opt in. Check the group's member list; anyone still marked as invited needs to accept the email invitation.
5. The release isn't live yet
The opt-in link only works once a release on the closed track has passed Google's review. Check Publishing overview for anything still in review.
6. Their country isn't selected
Testers in a country you didn't add under Countries / regions can't install the app. Add their country to the track.
7. They joined the wrong track
If you also run internal testing, make sure they used the closed track's opt-in link. Only closed testing counts for the requirement. Here's the difference.
8. The count hasn't caught up
Play Console's tester numbers aren't always instant. If everything above checks out, give it some time before you start changing things.
Quick reference
| Symptom | Most likely cause |
|---|---|
| Tester says "I joined" but the count didn't change | Didn't tap Become a tester, or a different account |
| Opt-in page says you're not invited | Email not on the list / not a group member |
| Opt-in link shows an error | Release not approved yet |
| Opted in but can't install | Country not selected |
| Count drops a few days in | Tester left the test. Why that's risky |
Fixing it without losing days
If someone isn't counting, fix it today: every day below 12 testers is a day that doesn't count towards your 14. If you can't fix a tester quickly, replace them. That's exactly why it pays to start with more than 12.
FAQ
How long does it take for a tester to appear in Play Console?
Often fairly quickly, but the numbers aren't always instant. If a tester has definitely opted in with the right account and still doesn't appear after a while, go through the checklist above.
Does a tester need to install the app to count?
What counts is being opted in to the closed test. Still, ask testers to install and use the app. You'll need their feedback for your production access application.
Can a tester use a Google Workspace or work account?
Yes, if that account is on your tester list or group and is the one signed in to Play Store on their phone. Some work accounts restrict Play Store access, so a personal Gmail is usually simpler.
Someone left the test. Do I have to start again?
If your count dropped below 12, the 14 days effectively start again from when you're back at 12 or more. If you still had 12 or more, you're fine.
Talk to a human, not a bot
Stuck on setup, Google's rules or your app? Message us and a real person from our team answers.
- Avg. reply under 5 minutes
- Any day of the week
Keep reading
- Closed vs Internal vs Open Testing on Google Play: What's the Difference?Google Play has three testing tracks. Here's who each one is for, how testers join, and which one counts for the 12-tester requirement on new personal accounts.
- Free vs Paid Google Play Testers: An Honest ComparisonFriends, tester exchanges, freelancers or a managed service? What each way of getting 12 Google Play testers really costs in money, time and risk.