"App not available" on a Google Play closed testing opt-in page

You send your opt-in link. A tester opens it in a browser and gets "App not available" instead of the page that lets them become a tester. In almost every case, Google Play is saying that the account in front of it isn't allowed into this test yet: wrong account, not on your list, not in your group, or the track isn't live for that person.

This page covers the browser opt-in page. Two related problems have their own pages:

• The tester already opted in, but the Play Store app on the phone says "Item not found": see Item not found in a closed test.
• The link itself fails, or you can't find an opt-in link in Play Console: see closed testing link not working.

Google doesn't publish the exact wording of this screen, and it follows the tester's language settings. Your testers may see a slightly different sentence. The causes are the same.

First: one tester or everyone?

To test it yourself, add a second personal Google account you own to the tester list (or to your group). Then open the link in a private browser window, signed in with that account only. If that works, your setup is fine and the problem is on the tester's side.

Causes and fixes, in the order to try them

1. The browser is signed in with another Google account

This is the most common one. Many people have several Google accounts in the same browser. The opt-in page looks at the account that's active, which isn't always the one they gave you. Only accounts on your email list, or members of your Google Group, can join a closed test (Play Console Help).

Fix: ask the tester to open the link in a private window and sign in only with the address you added. They must then use that same account in the Play Store app on their phone.

2. The address isn't on your email list

If you manage testers by email list, check three things on Test and release > Testing > Closed testing > Manage track > Testers:

• The address is spelled right. One wrong letter is enough.
• The list is actually selected for this track, and you clicked Save changes.
• You didn't overwrite the list. Google warns that uploading a CSV file replaces the addresses you added before, and that CSV files saved as UTF-8 with BOM aren't accepted (Play Console Help).

3. The tester hasn't joined your Google Group yet

Google is explicit: "For closed tests using a Google Group, users must join the group before opting into your test" (Play Console Help).

Fix: check the group's member list. If your group requires approval, the request waits until you accept it. Then the tester reloads the opt-in link.

If everyone in the group fails, check how the group is attached to the track. And if managed publishing is on, a newly added list or group is held back until you publish your changes from Publishing overview (Play Console Help). It must be entered with the Google Groups option, as [email protected], or as a Google Workspace group on your developer account's domain. Google doesn't describe Workspace groups from other domains as supported.

4. The test isn't live yet

The opt-in link only works once the app is published to the track. Google says the link appears only when the app status is "Published", not in "Draft" or "Pending publication". After you publish a test for the first time, the link "can take several hours to become available to testers" (Play Console Help).

Fix: look at the status under your app's name in Play Console (publishing statuses). If it's still in review, wait. If it was published less than a few hours ago, wait, then retry.

5. The tester's Play country isn't on the track

Country targeting is "based on where the user's Google Play account is registered, not their physical location" (Play Console Help). A tester living in France with a Play account registered in Morocco is a Moroccan user for your track.

Fix: open Closed testing > Manage track > Countries / regions and add the country. By default, testing tracks sync their countries with production. Click Unsync to set them separately. Don't ask the tester to change their Play country: Google makes them wait at least 90 days between changes (Google Play Help).

6. The tester is in your internal test

This one surprises people. Google says: "A user who opts into your app's internal test is no longer eligible to receive an open or closed test." They must opt out of the internal test first (Play Console Help).

Fix: remove that address from your internal testers, ask the tester to leave the internal test, then have them open the closed test link again. Keep your closed testers out of the internal list from the start.

7. Managed Google Play made the app private

On Test and release > Advanced settings > Managed Google Play, turning the feature on "makes the app private". It's meant for organizations that manage devices. For a regular closed test with personal accounts, leave it off (Play Console Help).

Fix: if you turned it on by mistake, turn it off and save. If you need it, add the organization of your testers to the track.

8. A work or school account

Google lets both Google Accounts and Google Workspace accounts join tests. But an administrator can restrict what a managed account does on Google Play. If a tester uses a work or school address and everything above checks out, ask them for a personal Google account instead.

What to send a tester who's stuck

Keep it short. Testers who get a long troubleshooting message often give up.

1. "Open this link in a private window and sign in with this address: …"
2. "If you joined our Google Group, check that your membership is accepted."
3. "On your phone, open the Play Store, tap your profile picture and switch to the same address."

The third step prevents the next problem: Item not found in the Play Store. For the full tester side of the flow, see how testers join a closed test.

When to contact Google

Contact Google through the Contact us link in Play Console Help when all of this is true:

• A fresh personal account you own is on the list or in the group.
• It fails in a private window.
• The status has shown "Published" for more than a day.
• The account's Play country is on the track.

Send the package name, the track name, the test account address and a screenshot of the error. For the bigger picture of the requirement, start from the Google Play closed testing guide.