DEV Community: Zenith605

Closed testing: "This item isn't available in your country" — fix your track's countries

Zenith605 — Thu, 17 Sep 2026 06:31:50 +0000

Your tester opted in to your Google Play closed test, but Play Store shows no Install button, just "This item isn't available in your country". That's the track's country setting. The opt-in page even looks fine:

But Play shows this instead of Install:

Nothing is wrong with the tester's phone or account, and there's nothing they can fix on their side.

In Play Console, go to Test and release → Testing → Closed testing, open the track, then the Countries / regions tab.

1. Read the filter

Open the filter and check that Not targeted is 0. This track is open in one country and blocked in the other 176, so almost anyone you swap tests with is locked out.

2. Select all

Press Edit countries / regions and tick the box at the top. No need to click through the list. Right after you tick it, every row still says Not targeted. That's normal until you finish step 3.

3. Save, then send it for review

Save only stores the change. Testers get in once you go to Publishing overview and send it for review.

4. Check again once it's through

Targeted (177) and Not targeted (0) means you're done.

Why you never saw it yourself

By default, test tracks follow production's countries:

"By default, your testing releases match the country availability that you've set up for production."

Your own phone is inside that one country, so you never see the problem.

Internal testing hides it one more time:

"Country targeting won't apply to apps on the Internal testing track."

So it works every time you try it yourself, and breaks the moment a stranger tries your closed track.

Testers can't work around it either. To change their Play country they have to be in that country, have a payment method from there, and then wait 90 days before changing again.

Unless you have a licensing reason, select every country. A test track isn't a launch. Whoever picks your app off a tester board could be anyone, anywhere, who happened to be awake.

Sources:

The full version, including tracks synced with production: actparty.app/guides/country-availability.html

ACT Party is a free app where developers test each other's apps to reach the 12 closed-test testers. If a tester can't install because of their country, it tells you right away.

Get it on Google Play

Google Play closed testing: joined the group but opt-in says "App not available" (6 checks)

Zenith605 — Thu, 17 Sep 2026 06:31:33 +0000

Your tester joined your Google Group, opened the opt-in link for your closed test, and got "App not available" instead of the Become a tester button.

First, ask the tester one thing: is the Google account that joined the group the same one signed in to Play Store on their phone? On a phone with two accounts this is the most common cause, and the page looks the same either way.

If the account is right, open Play Console, go to Test and release → Testing → Closed testing, open the track, then the Testers tab.

1. Is the track still on an email list?

Only one of Email lists and Google Groups can be on. If you made an email list first and added the group later, the choice is probably still on the list, and joining the group does nothing.

2. Switch to Google Groups

Type the full group address, ending in googlegroups.com. The address has to turn into a chip before Save lights up. If Save stays grey, press Tab.

3. If you use email lists, check the box

A list only counts while its row is ticked. It can hold the right people and show the right count and still do nothing.

4. Read every address back, letter by letter

Nothing warns you while you type. When Play does reject an address, you get one error on Save that doesn't say which row. And if the typo happens to be someone else's real account, it passes every check, so your tester just sees "App not available". With a Google Group, testers type their own address, so this can't happen.

5. Send the change for review

Saving tester settings doesn't apply them. They wait in Publishing overview until you send them for review. This is the most common reason a correct fix seems to change nothing.

6. Send the web link

At the bottom of the Testers tab, under How testers join your test, press Copy link next to Join on the web. That link, starting with play.google.com/apps/testing/, is the opt-in link. Send that one. Your store link is not an opt-in link.

What it looks like when it works

No screen ever says "success", so people keep pressing things again. This is what normal looks like:

The download link can take a few minutes to work. Tell the tester to wait instead of trying again.

Then keep them opted in for 14 days in a row

Play only counts testers who have been

"opted in continuously for the preceding 14 days"

If someone opts out and back in, their count starts over. When you swap tests with someone, agree on the end date up front. Day 15 is the first day they can leave.

Source: Play Console Help — App testing requirements for new personal developer accounts

The full version, including "no build on the track yet": actparty.app/guides/app-not-available.html

ACT Party is a free app where developers test each other's apps to reach the 12 closed-test testers.

Get it on Google Play

Android closed testing: fix "Content unavailable" on your Google Group

Zenith605 — Thu, 17 Sep 2026 05:52:09 +0000

You run your Android closed test through a Google Group, and a tester opens the group link and gets "Content unavailable". That means the group is private. Two settings fix it.

Open your group and go to Group settings → General. The two dropdowns you need are just below Shared labels, one scroll down.

1. Who can see group

Set it to Anyone on the web.

2. Who can join group

Set it to Anyone on the web can join. Not Anyone on the web can ask, the option right above it. With "can ask", you have to approve every tester by hand, and nobody can opt in until you do.

3. Save

Press Save changes. Google says the change can take a while to apply. If it still fails straight away, wait a bit before you change anything else.

4. Warn your testers about this screen

"You don't have permission to access this content" is about reading old posts in the group. That's a separate setting and has nothing to do with joining. The Join group button works. If you don't tell testers first, they see that line and leave.

5. Join once from a second account

From the account that owns the group, a broken group looks fine. Open it in another browser profile. If the member count goes up without you approving anything, it works.

Why this happens

Nobody got a setting wrong. This is how a new Google Group starts:

And Play Console asks for the group first:

"For closed tests using a Google Group, users must join the group before opting into your test."

So a group left on its defaults is a wall in front of your test, and the error your tester sees never mentions the group.

Source: Play Console Help — Set up an open, closed, or internal test

The full version, with Workspace groups and connecting the group in Play Console: actparty.app/guides/google-group.html

ACT Party is a free app where developers test each other's apps to reach the 12 closed-test testers.

Get it on Google Play