A Google Play internal app sharing link does not install the app
Internal app sharing link opens the Play Store but there is no Install buttonShort answer
An internal app sharing link fails for one of five reasons: the tester has not turned on internal app sharing in the Play Store, the tester is not authorized, the app is not visible to that tester, the link passed 100 downloads, or it expired after 60 days. Check each on the tester's device and in Play Console.
Fix it fast
1Find out which cause you have
Ask the tester to open Play Store, then Settings, then About, and check whether the Internal app sharing switch exists and is on. Without it, no link will install.
# Play Store > Menu > Settings > About > tap the Play Store version 7 times2Match what you see, then jump to its fix
- 1
The link opens but offers no installInternal app sharing is not turned on in the tester's Play StoreFix - 2
The tester's account differs from the one you addedThe tester is not authorized for the linkFix - 3
The store listing is not visible to the tester at allThe app is not available to that testerFix - 4
A link that worked for others fails for the newest testerThe link hit its 100-download limit or expiredFix
- 1
What does the error look like?
Internal app sharing link opens the Play Store but there is no Install buttonLink works for some testers and not for others
Cause 1 of 4
Internal app sharing is not turned on in the tester's Play Store
1Check
In the Play Store app the Internal app sharing switch only appears after the version number is tapped seven times.
# Play Store > Menu > Settings > About > Play Store version (tap 7 times)2Fix
Tap the version seven times, turn on the Internal app sharing switch that appears, and confirm with Turn on.
# Switch: Internal app sharing > Turn on3Verify
Open the link again; the install option is shown.
# Link opens the app page with InstallConfirmed by support.google.com
Cause 2 of 4
The tester is not authorized for the link
1Check
Links can be limited to authorized testers. Check the tester's email list in Play Console, and which Google Account the Play Store on the device uses.
# Play Console > Internal app sharing > Uploaders and testers tab2Fix
Add the tester's account to an email list, or set the link to be available to anyone who has it.
# Uploaders and testers > create email list > add address > Save3Verify
The tester opens the link from the added account and sees the app.
# App page loads with InstallConfirmed by support.google.com
Cause 3 of 4
The app is not available to that tester
1Check
The tester must be able to see the app's store listing. Common causes are that the app is not distributed in the tester's country, or it is only on a testing track the tester has not joined.
# Play Console: the app's country availability and the testing track tester list2Fix
Add the tester's country, or add the tester to the testing track.
# Add the tester's country to the app's distribution, or add the tester to the testing track3Verify
The tester can find the app in Play Store search or via the link.
# Listing visibleConfirmed by support.google.com
Cause 4 of 4
The link hit its 100-download limit or expired
1Check
Each link allows up to 100 users to download, and links expire 60 days after the upload date.
# Compare the upload date and number of testers who used the link2Fix
Upload the same file again on the internal app sharing page and send the new link.
# Play Console > Internal app sharing > upload the same file > share the new link3Verify
The new link installs on the tester's device.
# Install succeedsConfirmed by support.google.com
How do I stop it coming back?
- Send testers the steps to turn on internal app sharing together with the first link.
- Keep a shared email list of testers instead of adding people one by one.
- Re-upload the build before the 60-day mark if people still need it.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
Related fixes
Mobile apps
Testers cannot find or install the app from Play internal testing
The opt-in link is missing in Play Console for the internal test
An internal test is not searchable on Google Play.
4 causes, each with a fixMobile apps
adb cannot start because something already holds its port
adb start-server failed
The adb server must bind local TCP port 5037, and every adb client talks to it there.
2 causes, each with a fixMobile apps
The phone shows as unauthorized and Android Studio will not run the app
adb devices lists the phone but Android Studio cannot deploy to it
An unauthorized phone means it has not trusted this computer's RSA key.
3 causes, each with a fixMobile apps
Android Studio cannot pair the phone over Wi-Fi
The Pair devices over Wi-Fi dialog lists no device
Wireless pairing needs the phone on Android 11 or higher and on the same Wi-Fi network as the computer, with current Platform-Tools.
4 causes, each with a fixMobile apps
adb cannot connect to its daemon or start the server
* daemon started successfully *
The adb server is a background process on your computer that listens on TCP port 5037.
2 causes, each with a fixMobile apps
adb prints 'server version doesn't match this client; killing...'
adb server version doesn't match this client; killing...
adb runs a background server, and every adb command is a client.
3 causes, each with a fix