"Item not found" in the Play Store app during a closed test

The tester opened your opt-in link, became a tester, tapped the link to get the app, and the Play Store app on their phone answered "Item not found". The opt-in worked. What failed is the next step: the Play Store on that phone can't show your app to the account it's using.

This page is about the Play Store app on the phone. If the browser opt-in page itself refuses the tester, see "App not available" on the opt-in page. If the link doesn't open at all, see closed testing link not working.

Google doesn't publish the exact text of this message, and it depends on the phone's language. "Item not found" is how most testers report it.

Before anything else: don't search, use the link

Closed test apps don't show up in Play Store search. Google says that before an open test or production release, "testers cannot find your app by searching Google Play" and that you must share the app's Play Store URL with them (Play Console Help). A tester who types your app's name into the store will find nothing. That's normal.

One tester or everyone?

Causes and fixes, in the order to try them

1. The Play Store app uses a different Google account

This is the classic one. The tester opted in on a laptop with their personal Gmail, but the phone's Play Store is signed in with a work account or an old one. The opt-in is tied to an account, not to a person.

Fix: on the phone, open the Play Store, tap the profile picture at the top right and switch to the account that opted in. Then open the link again. If that account isn't on the phone, add it in the phone's settings first.

2. The tester never finished opting in

Opening the opt-in page isn't enough. Google says testers first get "an explanation of tester responsibilities and a link to opt in", and "each tester needs to opt in using the link" (Play Console Help). Some testers read the page, tap the download link and skip the button.

Fix: ask the tester to reopen the opt-in link in a browser signed in with the right account. The page should confirm they are a tester. Then they use the link to get the app.

3. The release isn't available yet

After you publish a test for the first time, Google says "the test link can take several hours to become available to testers", and "additional changes can also take several hours" (Play Console Help). During that window the opt-in may work while the Play Store app still can't show the app.

Fix: check that the status under your app's name is "Published" for the closed track (publishing statuses). If you published less than a few hours ago, wait and retry. If the release is still in review, nothing can reach testers until Google's review is done.

4. The Play Store app shows stale data

Sometimes the account and the release are right, and the Play Store on the phone just hasn't caught up. Google's own Play Help says that "clearing cache from Google Play Store is the most common solution to issues when you download apps from Google Play Store" (Google Play Help).

Fix, for the tester:

1. Touch and hold the Play Store app, then tap App info.
2. Tap Storage & cache > Clear cache.
3. If that's not enough, tap Clear storage. Google warns this can delete some Play Store settings, such as parental controls and password protection.
4. Open your link again.

Don't ask testers to clear Google Play services data. Google recommends it only as a last resort because it can remove saved payment and account data.

5. There's no release on the track your testers are in

Testers belong to a track through the email list or Google Group you set on that track. If they're on the default closed track but your build is on internal testing, or on an additional closed track you created with Create track, they have nothing to install.

Fix: open Test and release > Testing > Closed testing, find the track that holds your tester list or group, and check that it has an active release. If not, create one there and roll it out.

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

Country targeting follows "where the user's Google Play account is registered, not their physical location" (Play Console Help). The same cause can block the opt-in page. The fix is on the track's Countries / regions tab, as described on the "App not available" page.

7. The tester is also in your internal test

Google says a user who opts into your internal test "is no longer eligible to receive an open or closed test" and only gets the internal track's version (Play Console Help). Remove them from internal testing and have them leave it, then opt in to the closed test again.

It's not "Item not found"? Other messages

• "Your device isn't compatible with this version": the app is there, but your manifest or your device exclusions filter out that phone. See device not compatible.
• A price instead of an install button: Google says testers "must purchase paid apps when participating in open or closed tests" (Play Console Help). Plan for that before you invite people to a paid app.

When to contact Google

Write to Google through the Contact us link in Play Console Help if a fresh test account of yours, with nothing else on the phone, still gets "Item not found" more than a day after the closed track shows "Published", with an active release and its country targeted. Include the package name, the track name, the account and a screenshot.

For how this fits into the whole requirement, see the Google Play closed testing guide.