Google Play Opt-in Link Not Working? How to Fix It
Google shows a closed test opt-in link only when your app's status is 'Published'. If the link is missing or doesn't work for anyone, the release usually isn't published yet: changes may be waiting to be sent for review, blocked by an error, still in review or held by managed publishing. A first publication can also take several hours.
You copied the opt-in link from Play Console, sent it to your testers, and it doesn't work. Or there is no link to copy at all. In most cases the link itself is fine. The release behind it just isn't published yet. This guide explains how to check that in Play Console, using only what Google documents in its Help Center.
The facts here come from Google's articles Set up an open, closed, or internal test, Publish your app and Control when app changes are reviewed and published, plus the pages on pre-review checks and the Test and release overview linked in each section.
Is it the link, or one tester?
Start by separating two different problems. If nobody can use the link, or Play Console shows no shareable link to copy, the cause is almost always the release and its publishing status. That is what the rest of this guide covers.
If the link works for most testers but not for one person, look at that person's account instead. Google's setup article describes three tester-side conditions: a tester opted in to your internal test is not eligible for the closed test, a Google Group track needs testers to join the group before opting in, and every tester needs a Google Account or a Google Workspace account. Our closed testing setup guide lists those checks, and our comparison of testing tracks explains why an internal opt-in blocks the closed test.
When does Google show the opt-in link?
Google's rule is short. In Set up an open, closed, or internal test it says the opt-in link displays only when an app status is 'Published'. Apps in 'Draft' or 'Pending publication' status do not display an opt-in link. After you publish a test for the first time, the test link can take several hours to become available to testers, and additional changes can also take several hours.
So the useful question is not what's wrong with the link but whether your release has been published yet. This matters for your schedule. Google counts testers who have been opted in continuously for 14 days, so time without a working link is time no tester can start. Our guide to the 12 testers for 14 days rule explains how that count works.
How do you check your publishing status?
Google's Publish your app article says you can see your app's latest publishing status under the app's name and package name when you select your app in Play Console. Google describes three kinds of status: the app status (who your app is available to), the update status (whether your latest set of changes is live) and the item status (a single part of an update, such as one release).
The statuses that explain a missing or broken link are these:
- Draft (app status): your app has no presence on Google Play, either because you haven't published it yet or because it was rejected during review.
- No active releases (app status): you did not roll out updates on any track, or the updates were rejected.
- Changes not yet sent for review (update status): you made changes that have not been reviewed yet.
- In review (update status): Google is reviewing your update.
- Update rejected or App rejected (update status): Google notes that App rejected only applies to apps in Draft that you are trying to publish for the first time.
The Test and release overview page gives a second view. Google says a banner at the top shows the current status of your publishing queue, the same information as on the Dashboard, with a summary of changes in review or ready to be published. Below it, each testing track has its own card showing the release name and date when the track is in use.
Have your changes been sent for review?
Google explains that every change that needs review is added to the Changes not yet sent for review section of the Publishing overview page, and items are not sent for review until you click Send for review. Google's Prepare and roll out a release article confirms it from the release side: clicking Save adds your changes to the Publishing overview page, where you decide when to submit them.
Two details from Google's pages help here:
- Pre-review checks. According to Google's article on pre-review checks, these checks run automatically when you change your app and show up in the same section. All checks finish within 15 minutes. You can click Send for review while they are still running, and Play Console submits your changes automatically if no critical issues are found.
- After a rejection. If an update was rejected and you made changes to fix it, Google says your changes aren't sent for review automatically. You must go back to the Publishing overview page and click Send for review again.
Is an error blocking the release?
Some problems stop a release before it can be published at all. Google documents three places where they appear:
- Errors summary. For a draft app, Google says that if you see the heading "Errors summary" at the top of your release's review summary page, you can click Show more for the details. You can't publish your app until the errors are resolved. Warnings and minor issues alone don't block publishing, but Google recommends addressing them.
- Critical pre-review issues. Critical issues must be fixed before you can proceed. Other issues can be deferred by clicking Proceed anyway, but mandatory checks, such as missing app content declarations and required app details, cannot be skipped.
- Errors on the Test and release overview. In the "For your next release" list, Google describes errors as critical issues that stop you sending a new release for review until they are resolved. Its example is a missing Data safety declaration.
How long can review take?
If your update is in review, the link will not work until the review is complete and the changes are published. Google's publishing control article says processing can take a few hours or up to seven days, or longer in exceptional cases, depending on the review time your app is subject to. Google recommends planning a buffer of at least a week between submitting and going live. Its Publish your app article adds that some developer accounts get a more thorough review, with review times of up to seven days or longer. Our closed testing timeline puts these review times next to the 14 days.
One more detail affects new submissions. Google says the review turnaround is counted from the last change you submitted, so submitting a change while others are in review may push your app to the back of the review queue. If your test release is already in review, think twice before sending small extra changes.
Is managed publishing holding changes back?
With managed publishing turned on, approved changes wait in a Changes ready to publish section until you click Publish changes on the Publishing overview page. Google says the update is then published on Google Play within a few minutes. Google also notes you can't use managed publishing when you publish an app for the first time.
For testers, the important part is what it holds back. Google's list of held changes includes full and staged rollouts of your releases, and changes to how testers are configured for a track, for example setting a new email list or Google Group as the track's testers. Google lists changes to the membership of an email list or Google Group already used by a testing track as an exception that is not held back. Adding a person to your existing list doesn't wait for you, but switching the track to a different list does.
Frequently asked questions
Why is there no opt-in link for my closed test?
Google displays the opt-in link only when the app status is 'Published'. Apps in 'Draft' or 'Pending publication' status do not display it. Check whether your changes are still waiting to be sent for review, are in review, or were rejected.
How long after publishing does the opt-in link start working?
Google says that after you publish a test for the first time, the test link can take several hours to become available to testers. Later changes can also take several hours.
Do I have to send my changes for review myself?
Yes. Google says changes that need review are added to the 'Changes not yet sent for review' section of the Publishing overview page and are not sent until you click Send for review.
How long can the review of a test release take?
Google says processing can take a few hours or up to seven days, or longer in exceptional cases, depending on the review time your app is subject to. Some developer accounts get a more thorough review.
Does managed publishing hold back changes to my tester list?
It depends on the change. Google says setting a new email list or Google Group as a track's testers is held back, while changes to the membership of a list or group already used by a testing track are not.