Troubleshooting
"Testing Version Hasn't Been Published": Tester Fix
Testers see "app not available" or "testing version hasn't been published" in Google Play? Fix the release, account, list and country settings.

On this page · 7 sections
When a tester sees that the testing version of your app has not been published yet or is not available for their account, Google Play is telling you one of two things. Either the closed release is not live on the track yet, or Google Play does not see this tester's account as an opted-in tester who can install it. Check that the release is available, that the tester's account is on the list for that exact track, that they opted in with that account, and that their country and device are allowed. Google's 12-tester, 14-day closed testing rule applies to personal Play developer accounts created after 13 November 2023; organization accounts are exempt (Play Console Help 14151465).
Fixes for the developer
- Open the closed track in Play Console and check the release status. If it is a draft or still in review, the app is not available to testers yet.
- Make sure the release was rolled out to the same closed track the testers joined. A release on internal testing does not help closed testers.
- Open the Testers tab and confirm the tester's email list or Google Group is ticked for this track and saved.
- Check Countries and regions for the track. Add the tester's country if it is missing.
- Check the device catalog or your app's minimum Android version. A tester on an older or excluded device may see the app as not available.
- Send the web opt-in link again and ask the tester to accept it with the correct account.
Fixes for the tester
- Open the web opt-in link and make sure it says you are a tester. If it offers a button to become a tester, press it.
- On your phone, open the Play Store, tap your profile picture, and check which Google account is active. Switch to the account that opted in.
- If you joined through a Google Group, check that you are a member of that group with this same account.
- Clear the Play Store cache in your phone's app settings, then open the store link again.
- Wait a little while and try again. New tester access can take some time to show up.
Why it shows for some testers and not others
If most testers can install and one cannot, the problem is probably on that tester's side: wrong account, not in the group, or a device or country that is excluded. If nobody can install, look at the release status and the track first.
A useful test is to opt in yourself with a personal Google account that is on the list. If it works for you, the setup is fine and you can focus on the individual tester.
Write a short message testers can follow
Before you send the opt-in link, tell testers which account to use, what the opt-in page looks like, and what to do if they see this error. A two-line message saves a lot of back and forth.
Other messages testers may see
Sometimes the Play Store simply says the item is not found, or shows the listing without an install button. These often have the same causes: the tester has not opted in, is using a different account, or is in a country or on a device the track does not cover.
If a tester opted in on a computer, ask them to open the Play Store link on their phone afterwards. The opt-in is tied to the account, so it works on any phone signed in with that account.
FAQ
Questions about this topic
The release is approved. Why do testers still see the error?
Check that the release is on the same closed track they joined, that their account is on that track's tester list, and that their country is included.
Does this error stop the 14-day count?
The requirement counts opted-in testers. If a tester cannot opt in or install, they are probably not being counted, so fix it early.
Can a tester use a work Google account?
Sometimes work accounts have restrictions. A personal Google account is usually the simplest choice for testing.
Sources
Official references used
- App testing requirements for new personal developer accounts (Google Play Console Help)
Continue
Choose the next step
Related
Next pages to read
Rather not recruit testers yourself?
Our managed closed test runs 14 testers for 16 days. Google requires 12 testers for 14 days (for personal Play developer accounts created after 13 November 2023; organization accounts are exempt); the extra 2 testers and 2 days are our buffer.