How to Share Your Google Play Closed Testing Link
Where the opt-in link is, exactly what to send with it, the tester's three steps and a tracking sheet for 14 days.
Read the guide →Google Play Closed Testing Link Not Working? Fixes
Quick answer If your closed testing link is not working, check that the app is Published, a release is rolled out, the tester's Google account is on your list, and their country is selected, then wait a few hours.
You copied the opt-in link from Play Console, sent it to your testers, and now the messages are coming back: “item not found”, “the app is not available”, or simply nothing happens. With 14 days to complete and at least 12 testers needed, every day of delay hurts. The good news is that the link itself is almost never the problem. The cause is nearly always one of eight things in your track settings or in the tester's Google account, and you can check all eight in about ten minutes.
Closed testing link not working: the 2-minute checklist
Do these in order. Stop when the problem is fixed.
- Is the app Published?Google says the opt-in link appears only when the app status is Published. If your Dashboard shows a draft or an app still waiting for review, the link cannot work yet.
- Is a release rolled out to the closed track?Open Testing > Closed testing, open the track and confirm there is an active release, not a draft.
- Is your tester list ticked?On the Testers tab, the email list or Google Group must be selected for this track, and you must click Save.
- Is the tester's email on that list?Compare the exact address, character by character, with the Google account the tester is using.
- Is the tester's country selected?Open the Countries/regions tab and confirm the tester's country is included.
- How old is the link?If you published only a few hours ago, wait. Google says first-time links can take several hours.
How is the closed testing link supposed to work?
It helps to know what Google actually describes, so you can tell a real fault from a normal delay. According to Google's testing help page:
- After a tester clicks the link, they receive an explanation of their responsibilities and a link to opt in. Each tester has to opt in using the link.
- Closed tests are not searchable on Google Play. The link is the only way in.
- For a closed test, testers come from email lists, Google Groups or organizations that you select on the Testers tab.
- Testers need a Google Account or Google Workspace account to join.
- If you use a Google Group, members must join the group before they can opt in.
- Devices receive the highest version code that is compatible with them and published to a track they are eligible for.
That list already explains most failures: the wrong account, a missing group join, a release the device cannot use, or a track that is not live yet. If you have not built your tester list yet, follow our guide to adding testers in Play Console and then come back here.
Symptoms, causes and fixes
Google does not publish a complete list of error screens, so this table combines what its help pages document with the causes developers most often report. The right-hand column tells you exactly what to try.
| What the tester sees | Most likely cause | What to do |
|---|---|---|
| “Item not found” or a page that cannot be opened | The signed-in account is not on your list or group, or the app is not Published yet | Confirm the account email, confirm the status is Published, resend the link |
| “The app is not available in your country” | The tester's country is not selected for the track | Add the country on the Countries/regions tab and save |
| “Your device isn't compatible with this version” | The release does not support the tester's device or Android version | Check your minimum SDK and supported devices, or use another phone |
| The link opens but there is nothing to install | No release is rolled out to the closed track, or it is still propagating | Roll out the release and wait a few hours |
| The tester cannot opt in at all | They are signed in with a different Google account | Switch accounts in the browser and in the Play Store, then reopen the link |
| A group member cannot join | They have not joined the Google Group yet | Ask them to join the group first, then open the link |
| The tester sees an older version or no update | They are also opted in to internal testing, or the update is still propagating | Opt out of internal testing, wait a few hours, update the Play Store |
| The link worked yesterday and stopped | The track was paused, or the list was replaced by a new CSV upload | Check the track status and upload the full list again |
Fix it in Play Console
Confirm the app is Published and the release is live
Open your Dashboard. If the app is still a draft, finish the outstanding setup tasks, then create and roll out a release to the closed track. Google's publishing status page explains the statuses. If the release summary shows errors, you cannot publish until they are fixed. Warnings do not block publishing, but fix them where you can.
Check the track, list and countries
- Open the trackGo to Testing > Closed testing and click Manage track.
- Open the Testers tabMake sure at least one email list, Google Group or organization is selected, and that the tick is saved.
- Check the feedback channelGoogle asks for a feedback URL or email address, which appears on the opt-in page.
- Check Countries/regionsConfirm the tester's country is targeted.
- Copy a fresh linkCopy the link again and send that one, as plain text, with no extra characters at the end.
Get the CSV right
If you upload testers as a CSV file, remember Google's rules: put each address on its own line with no commas, avoid UTF-8 with BOM (Play Console does not accept it), and upload the whole list every time, because uploading overwrites the addresses you added before. A common mistake is uploading only the new testers and wiping everyone else.
Fix it on the tester's phone
- Use the right accountOpen the Play Store, tap the profile picture and check which Google account is active. It must be the address on your list.
- Open the link in that same accountUse the phone's browser or Chrome with only that account signed in. A second Gmail account in the same browser is the most common cause of a wrong-account error.
- Join, then installAfter opting in, the tester should go to Google Play and install the app. Pull to refresh or search for the app name.
- Update or restart the Play StoreOpen the Play Store settings, check for updates, force stop the Play Store and reopen it.
- Check the connectionTry Wi-Fi and mobile data. Corporate or school networks can block parts of Google Play.
- Try again laterIf the app was published only a few hours ago, ask the tester to try again tomorrow.
The internal testing trap
Google notes that a user who is opted in to internal testing cannot receive open or closed test versions until they opt out of the internal test. If you added the same colleagues to both tracks while building your app, they may be stuck on an older internal build. Remove them from the internal list, or ask them to opt out, then reopen the closed testing link. Our guide to internal vs closed testing explains how the tracks differ.
A message for a stuck tester
Copy and send: Hi! Please open this link while signed in to the Google account I added: [opt-in link]. Tap to join the test, then open Google Play and install the app. If you see an error, tell me which Google account you are using and send a screenshot. Thank you!
Should you wait or act?
| Situation | What to do |
|---|---|
| App published less than a few hours ago | Wait. Google says first-time links can take several hours. |
| A release was rolled out today and testers see no update | Wait several hours. Later changes can also take time. |
| The same error for every tester | Check status, release, list and countries in Play Console. |
| The error affects only one tester | Check that person's account, device and country. |
| It has been more than a day and nothing changed | Rebuild the list, copy a fresh link and test with one tester first. |
How to prevent it next time
- Ask testers for the Gmail address they actually use on their Android phone before you build the list.
- Test the link with one friendly tester before you send it to everyone.
- Add 15 to 20 testers, not just 12, so a few failures do not stop your 14-day count. See how to get 12 testers.
- Keep a simple sheet: name, email, date joined, date confirmed. See how to share the closed testing link.
- Write down who left and replace them quickly. See what to do if testers leave.
If your testers have joined but Play Console still shows a low number, the problem is a different one. Read why testers are not counting. If you would rather not manage tester accounts yourself, our team supplies real Android testers and handles the opt-in for you.
Part of a series: this article is one chapter of Google Play Closed Testing: The Complete Guide. Start there for the full roadmap from setup to production.
Sources
- Google Play Console Help: Set up an open, closed, or internal test
- Google Play Console Help: App testing requirements for new personal developer accounts
- Google Play Console Help: Publishing overview and statuses
Frequently asked questions
Why does my closed testing link say “item not found”?
Google does not publish a full list of error messages, but the usual causes are that the signed-in Google account is not on your tester list or group, the app is not yet in the Published state, the release has not been rolled out, or the link is too new. Google says the opt-in link only appears when the app status is Published and can take several hours to work after a first publication.
How long does a closed testing link take to start working?
Google says that after you publish an open, closed or internal test for the first time, the test link can take several hours to become available to testers, and later changes can also take several hours. Internal test bundles become available within minutes.
Can anyone with the link join my closed test?
No. For a closed test, testers must be on one of the email lists or Google Groups you selected for the track, or belong to an organization you chose. Open tests are the ones anyone can join.
Do my testers need an Android phone?
Testers install the app from Google Play, so they need a device that can run it. Google also gives each device the highest compatible version code published to a track it is eligible for, so an app that does not support a tester's device will not be offered to them.
My link works for me but not for my testers. Why?
You are signed in with the developer account that owns the app, so you are not a good test. Ask a tester to confirm which Google account they are signed in with, and compare it with the email on your list.
Does uploading a new CSV add to my list?
No. Google says uploading a CSV file overwrites any email addresses you previously added, so upload the full list every time. Put one address per line with no commas, and avoid UTF-8 with BOM, which Play Console does not accept.
