Closed testing opt-in link not working: a checklist
If your testers can’t opt in, you’re losing days. Go through these items in order. Each comes from Google’s help documentation, plus a few clearly marked practical tips.
1. Did you wait for first-publish delay?
Google says: “After publishing an open, closed, or internal test for the first time, the test link can take several hours to become available to testers. Additional changes can also take several hours to become available.” Check that the release is actually published (not just saved as a draft), then wait.
2. Is the tester using the right Google account?
For an email-list closed test, the tester has to use the Google account whose address you added. A common pitfall (our tip, not a Google statement): the tester taps the link on a phone signed in with a different account. Ask them to switch accounts, or add the address they actually use.
3. Did you add them to the track you’re sharing?
On Test and release › Testing › Closed testing, select the track, open the Testers tab, and confirm the list is selected for that track. Then copy the link from that track.
4. Google Groups: did they join the group first?
If you use Google Groups, Google says only members of the specified groups can join your test, and the group address format is yourgroupname@googlegroups.com. The tester must be a member before they can opt in.
5. Is the tester in an internal test already?
Google: “A user who opts into your app’s internal test is no longer eligible to receive an open or closed test. To access an open or closed test, the user must first opt out of the internal test and then opt in to the open or closed test.” If you’ve been using internal testing with the same people, this is likely it.
6. Organization or managed Google Play accounts
To add testers from an organization using managed Google Play, Google says to turn on the Managed Google Play option under Advanced settings, which makes the app private. See the Setup article for details.
7. Paid apps
For paid apps, Google says testers must purchase the app when participating in open or closed tests (internal testers can install for free).
8. Have they actually opted in?
Opening the link isn’t enough; the tester needs to accept the invitation on the opt-in page and then install from Play. Remember the 14-day clock needs them opted in, and they must stay that way.
Still stuck? Use Help in Play Console to contact Google, and note the date/time you published so you can describe the delay accurately.
Want help keeping the streak alive?
Day15 is a do-it-yourself kit we’re building for developers going through this: an opt-in streak tracker, tester reminder emails, Data safety answers drafted from your app’s permissions, a privacy policy, and drafted production-questionnaire answers. It’s in development, nothing is charged today, and the early-bird price is planned at around $15 one-time.
Sources (Google’s own help pages)
- Set up an open, closed, or internal test
- App testing requirements for new personal developer accounts
Facts about Google Play rules on this page were checked against these pages on Oct 29, 2026. Google changes its policies and Play Console UI; if something here disagrees with Google’s page, trust Google. Practical advice is labelled as ours. This is an independent guide by Anchor Point Apps LLC, not legal advice, and not affiliated with or endorsed by Google.