“Item not found” for every tester: no release is live on the track
Every tester gets “Item not found” because no release is published on the closed testing track yet. Roll out a release there and wait for the “Published” status.
What you see
Every tester gets “Item not found”, and none has managed to install the app.
Why
Testers can only get a release that is live on the track they belong to. Usually the app is still a draft, still in review, or its changes were never sent for review. A rejected first release also keeps the app in draft. Sometimes the release sits on internal testing, or on another closed track than the one with the testers' group.
What to do
- Look at the status under your app's name in the Play Console.
- Open “Publishing overview”. If changes wait under “Changes not yet sent for review”, click “Send for review”.
- If managed publishing is on, approved changes wait under “Changes ready to publish” until you click “Publish changes”.
- Check that the release is on the same closed track as the testers' group.
- Once the track shows “Published”, give it time: Google says a test can take several hours to become available after its first publish.
What Peerbeta does
When at least three testers can't find the app and none has installed it, the diagnosis sends you an alert that points to the release rather than to the testers.
Was this helpful?
Your feedback shapes what we write next.
“Item not found” for several testers: the group isn't on the track
Next →“Item not found”: the wrong Google account in the Play Store