"Item not found." in Google Play Closed Testing: A 5-Step Debug Checklist

You send your closed testing link, and a tester replies with a screenshot: a satellite, the words "Item not found." and a Try again button.

Your app is almost certainly fine. Google Play hides closed test apps from every account it doesn't recognize as a tester, and "Item not found." is how it says "you're not on the list (yet)".

The fastest way to debug it is to answer one question first.

Start here: who can't open it?

Who sees "Item not found."	Where the problem usually is	Start with
One or a few testers	Tester side: account, sync, opt-in	Steps 1–3
Every tester, including your own second account	Developer side: release, review, countries	Steps 4–5

If you're not sure, run the self-test at the end of this post. It takes about 15 minutes and tells you which side to look at.

What has to be true for a tester to get in

Two things, both at once:

1. The tester's Google account is on your tester list. With a Google Group, that means the account is a member of the group you added on the Testers tab.
2. Your closed testing track has a live release that's available in the tester's country.

With a Google Group, a member can install straight from the Play Store listing (play.google.com/store/apps/details?id=<package>), and the install counts as opting in. The other route is the opt-in link (play.google.com/apps/testing/<package>) and its "Become a tester" button. If either condition above fails, both routes end in "Item not found."

Tester side

Step 1: Is the Play Store using the account that joined the group?

This is the most common cause by far. Many phones are signed in to several Google accounts. The tester joins the group in a browser with account A, but the Play Store app is on account B.

Fix: In the Play Store, tap the profile picture (top right) and switch to the account that joined the group. Then open the link again.

Step 2: Has Google had time to sync?

Joining a group doesn't work instantly. In our experience the Play Store usually recognizes a new member after 10–15 minutes, occasionally longer.

Fix: Wait, then try again. Leaving and rejoining the group doesn't speed it up. If it still fails after an hour, go back to step 1 or move on to step 3.

Step 3: Try the opt-in page instead

Now and then the Play Store listing keeps showing "Item not found." even though the account is in the group.

Fix: Open the opt-in link (play.google.com/apps/testing/<package>) in a browser signed in with the same account, tap "Become a tester", then go back to the Play Store and install. It's the classic flow and still works.

Developer side

Step 4: Is there a live release, and were your changes approved?

If nobody can open the link, check your own setup first:

• Releases tab of the closed testing track: you need a release that's available to testers, not one that's still in review or saved as a draft.
• Publishing overview: adding a Google Group or changing countries is a change that needs review. If you see changes that haven't been sent, click Send changes for review. Until they're approved, the new group's members can't see the app.

Step 5: Is the tester's country included?

The closed testing track has its own Countries / regions tab, separate from production. If a tester's Play Store country isn't selected, they get "Item not found." even when everything else is right.

Fix: Select all countries/regions for the closed testing track. It doesn't affect where your production release goes later, and it removes a whole class of errors.

The self-test: find out which side it is

1. Take a second Google account you control and join your tester group with it.
2. Wait 15 minutes.
3. On a phone or browser signed in with that account, open your Play Store listing.

If your own second account can install the app, your setup is fine and the problem is on the tester's side (steps 1–3). If you get "Item not found." too, fix steps 4 and 5 before asking testers to try again.

Checklist

Testers

• The Play Store is signed in with the account that joined the group
• Waited 10–15 minutes after joining
• If the listing still fails, tried the opt-in link and "Become a tester"

Developers

• The closed testing track has a release that's available to testers
• Publishing overview has no unsent or unapproved changes
• All countries/regions are selected for the closed testing track
• The Testers tab lists the group your testers actually joined

Why this happens so often in test-for-test swaps

In most swap threads, every developer creates a separate Google Group for their own app. To test 12 apps, you join 12 groups, wait for 12 syncs, and get 12 chances to join with the wrong account. That's where most "Item not found." errors come from.

How BetaLobby avoids most of this

BetaLobby is where indie Android developers team up to get their 12 testers: 16 developers form a team and test each other's apps for 14 days. It's built around the steps above:

• One shared group for every app: [e-mail]. Add it to your closed test once (next to any groups you already have), join it once, and you can install every app on the platform. No new group, and no new sync, for each app.
• The right account, checked for you: BetaLobby checks that the Google account you signed in with is in the group, and if the Play Store says "Item not found.", it tells you which account to switch to (step 1).
• Your setup is checked before testers see it: when you submit, BetaLobby checks that your app is actually visible to testers. If Google is still reviewing your tester changes, it re-checks automatically every 20 minutes and notifies you when it passes (step 4). It also checks a few countries to catch region limits (step 5).
• No screenshots: installs and daily check-ins are verified automatically.

It's free, with no paid plan.

---

Originally published on betalobby.com.