In this note
Short answer
Do not restart the test yet.
First confirm that the tester used the same Google account for the group, the Play opt-in, and the Play Store. Then confirm that the release is available on the exact closed track they joined. Only after those checks should you assume the count is genuinely empty.
The short answer
Google Play counts opted-in testers for a specific app and track. It does not count someone just because they joined a Google Group, opened an opt-in link, or installed a different build.
The dashboard can also take time to reflect a new opt-in. A temporary zero is frustrating, but it is a signal to diagnose the path from group to track to install—not proof that every tester disappeared.
- A group member is not automatically an opted-in Play tester.
- An opt-in must use the Google account that is active in Play Store.
- The app release must be available to that tester on the selected track.
- The count you see can lag behind a recent change.
Check the account chain first
Ask one tester to walk through these checks on the same Android phone. One successful end-to-end check is more useful than ten guesses.
- 01
Look at the Play Store account
Open Play Store, tap the profile photo, and note the exact Gmail account currently selected. This is the account that must be used for every next step.
- 02
Join the Google Group with that account
If your test uses a group, open the group invite while signed into the same Gmail. Joining from a browser logged into another account is a common silent failure.
- 03
Open the opt-in link
Use the link generated for the correct closed-testing track. The page should clearly confirm that the account is now a tester before the person tries to install.
- 04
Install from the Play listing
Install the app from Google Play while that same account remains selected. The app opening successfully is a useful final check, but the opt-in step is the important one for the count.
Check the test track
A valid tester can still see an empty-looking result when the release is on a different track from the link they received. In Play Console, open the app and verify the track, release status, tester method, and the exact opt-in URL you shared.
If you uploaded a new build, confirm that the release is available rather than still in review, paused, or limited to a different country or tester list. Keep your instructions tied to one track so testers do not have to guess.
- The app package name in the link matches the app you are checking.
- The closed-testing track has an available release.
- The tester method is the one your invite explains: group or individual list.
- The tester is not looking at an internal-testing link by mistake.
“The fastest fix is a reproducible path: one account, one group, one opt-in link, one Play listing.”Read the count correctly
Treat Play Console as the source of truth for the current tester count, but give a recent opt-in time to settle before making another large change. Keep a small log with the tester’s Gmail, the time they opted in, the track, and whether the opt-in page confirmed success.
This log also helps you spot a real drop. If a person opted in and later opted out, uninstalling the app is not the same as leaving the test; ask them to check their Play testing status before you replace them.
Before restarting the test
- 01
Send the three-link block
Give testers the group link, the Play opt-in link, and the install link in that order. Put the same-Gmail warning directly above the links.
- 02
Recruit a small buffer
If your account has a minimum tester requirement, do not stop at the minimum. A few extra people protect the test from normal drop-off.
- 03
Check the count daily
Record the count and any changes rather than relying on memory. A simple daily check is enough to distinguish a display delay from a genuine opt-out.
Where MeldPlay fits
Make the testing path visible.
MeldPlay helps Android creators publish a clear testing listing and helps early users discover what needs testing. It cannot change Play Console’s rules or guarantee approval, but it can make the handoff between creator and tester easier to follow.