Closed testing opt-in link not working: what to check
Updated
A broken opt-in link costs you days you cannot get back: every tester who cannot join is a tester who is not counting toward the fourteen. The error messages Google shows are vague, but the causes are few, and the symptom tells you which one you have. Start with the symptom below that matches yours.
This guide is about testers who cannot get in at all. If they got in and Play Console still shows fewer than twelve, that is a different problem, covered in testers opted in but your count is short. What the twelve are counting toward is set out in Google Play's 12 testers, 14 days requirement.
Symptom 1: the link fails for everyone, including you
If nobody can open the link — a 404, "item not found", or a page that says the test is not available — the problem is the release, not the testers.
- The release is still in review. A closed-track release is reviewed before it reaches testers. Until it is approved, the opt-in page has nothing to offer. Check the release status on the closed track in Play Console.
- It was approved but never published. If managed publishing is turned on, approved changes wait for you to press publish in Publishing overview. This catches a lot of people who turned it on once and forgot.
- You published a few minutes ago. Google's own documentation says the test link can take several hours to become available, and later changes can take several hours to apply as well. Wait before debugging anything else.
Symptom 2: it works for you but not for some testers
When the link works for some accounts and not others, look at who the tester is signed in as, then at whether that account is actually on your list.
- Wrong account. The opt-in page acts on the account signed in to the browser or the Play Store — not the one the tester thinks they gave you. People with a work and a personal account hit this constantly. Ask them to open the link in a private window and sign in with exactly the address on your list.
- Not on the list, or the list is not attached. With email lists, the address must be on a list and that list must be ticked for this track. A typo in one character still saves.
- Google Group not joined yet. With a Google Group, the tester has to join the group first, with the same account they will use to opt in. Joining with one account and opting in with another fails silently.
- Changes not live yet. Adding a tester is a track change, and track changes can take hours to propagate — and under managed publishing they wait for you to publish them.
Symptom 3: they opted in, but the Play Store says "not available"
This one alarms people most and is usually the least serious. Opting in and installing are separate steps; a tester can be successfully opted in and still unable to install.
- Country or region. Closed testers follow your release's country and region availability. A tester outside those countries can opt in and then see "not available". Add their country, or recruit within the countries you ship to.
- Device compatibility. A minimum SDK above the tester's Android version, or a device excluded in the device catalog, produces the same message. Check the tester's device against your app's requirements.
- The Play Store has not caught up. After opting in, have the tester follow the Play Store link shown on the opt-in page, on the phone, signed in with the same account. Searching the store by name often does not find apps in closed testing.
Symptom 4: they were sent the wrong link
The opt-in link and the store listing link look alike and are not the same. The
one testers need is the opt-in link from Testing → Closed testing → Copy
link in Play Console. It starts with play.google.com/apps/testing/. A link to
play.google.com/store/apps/details is the store listing, and on its own it
will not opt anyone in.
After the fix: confirm they are counted
A tester getting through the opt-in page is not the finish line. The only number that matters is the one Play Console shows for the closed track, so check it rather than taking the tester's word for it — here is where to look.
If you are still setting the track up, the order of steps matters more than it looks: setting up a closed test in Play Console walks through it so that the link works the first time.