Seat accepted, but still no install confirmed

Often the Play Store on the phone uses another Google account, or the app was never opened from the tester app. Check the account, then tap “Open the app” in the tester app.

J
Written By JordanLast updated 1 hour ago

What you see

A tester accepted the seat more than a day ago, and Peerbeta still shows no verified install.

Why

Two causes come back most often. The Play Store on the phone uses another Google account than the one in the test, so the app can't be installed. Or the app is installed, but the tester never opened it from the tester app, and that opening is what proves the install.

What to do

For the tester:

  1. In the Play Store, switch to the Google account you use with Peerbeta, then get the app.
  2. Open the tester app and tap “Open the app”.
  3. On Android 11 or 12, if the tester app asks for it, open the app from your home screen, take a screenshot and tap “Send a screenshot of the app”.

For the developer: give the app's launch activity when you create the test. Without it, testers on Android 11 and 12 can only prove their install with a screenshot.

What Peerbeta does

The diagnosis flags seats accepted more than 24 hours ago without a verified install. 48 hours after the invitation, the seat is freed without penalty, and until day 2 of the test Peerbeta invites a replacement.

Was this helpful?

Your feedback shapes what we write next.

← Previous

“Item not found”: the wrong Google account in the Play Store

Next →

“You're a tester”, but no Install button

Related articles

“You're a tester”, but no Install buttonThe release is still on its way: Google says it can take several hours after a test's first publish. Wait a few hours, then open the link again.“Item not found”: the wrong Google account in the Play StoreThe Play Store on the phone uses another Google account than the one in the test. Switch accounts in the Play Store, then open the test link again.“Item not found” for every tester: no release is live on the trackEvery 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.“Item not found” for several testers: the group isn't on the trackSeveral testers get “Item not found” from the start because the testers' group isn't on the closed testing track, or was entered as an email list. Add it under “Google Groups” in the track's Testers tab.