Tester Access
Your tester says the opt-in link doesn't work
A tester messages you: "no access", "Item not found", or the Play Store simply can't find your app. Almost every time, the app is fine and the problem is in the account, the list or the track. Work the checks below in order — they're sorted by how often they're the cause and how fast they are to rule out.
The checks, in the order worth doing them
1. Wrong Google account on the device
The tester must open the opt-in link while signed into the exact account on your list. Most phones carry several Google accounts, and the browser often defaults to the wrong one. Confirm in under a minute: ask them which account the link opened as. Note the account can be a Google Workspace address, not only Gmail.
2. The address isn't on the list you think it is
Compare it character by character in Play Console → Testing → Closed testing → Testers. Typos and a wrong-track list are both common. If you manage testers through a Google Group, membership of that group is what counts — being on a list elsewhere does nothing.
3. The tester is on a different track
Someone opted into your internal test can find themselves ineligible for the closed test until they leave it. If a tester was helping you earlier in the process, check this before assuming the link is broken.
4. No live release on that track
A build that is uploaded but still in draft, in review, or held by managed publishing is not available to testers. Check the release state on the closed testing track itself. This is not a delay — nothing will change until the release is actually live.
5. They were sent the store link instead of the opt-in link
The order is not optional: join through the opt-in URL first, then reach the install page. A plain Play Store listing link will look broken to someone who hasn't joined. Also check the opt-in URL carries the correct package name.
6. The build isn't available to that device or country
Availability is decided by country targeting, minimum SDK, required hardware features, form factor, ABI and any device exclusions — not by runtime permissions. A tester on an old or unusual device may be genuinely ineligible. If the app is paid, the tester also has to complete the purchase before installing.
7. Only now: propagation
Track changes can take a little time to reach every tester. Check this last. It's the explanation people reach for first, and it's usually covering one of the six causes above.
The message to send a stuck tester
Most back-and-forth disappears if you send this instead of just re-sending the link:
Why this is worth ten minutes of your time
Google counts the 14 days per tester. A tester who never gets in never starts their clock — and a replacement recruited later has to complete their own 14 consecutive days. An access problem you leave unsolved on day 2 is an annoyance; the same problem discovered on day 13 costs you the cycle for that slot.
Related: the 12 testers requirement explained, what to do when production access is refused, and what a completed cycle should produce.
Tired of debugging tester access?
We enroll the testers and confirm every one of them is actually in.
You send the opt-in link, we handle recruitment, enrollment and daily checks for the full 14 days. Plans from $180, worldwide.
Start your testing cycle