Testers are stuck at the app's sign-in screen
The app asks for an account and testers have none. Give a test account in your Peerbeta test and in the Play Console's “App access”.
J
Written By JordanLast updated 1 hour ago
What you see
Testers write that they can't get past the sign-in screen, or that the app asks for an account they don't have.
Why
Your app needs an account, and the test gives none. Testers can't create one, or creating it needs something they don't have, such as an invitation. Google's reviewers run into the same wall.
What to do
- Create a test account that needs nothing from you to sign in, such as a code sent to your own phone.
- Give it in your Peerbeta test, so the testers of the test can sign in.
- In the Play Console, fill “App access” with the same credentials and the steps to sign in. Google's reviewers need them, and so does the production access review.
- Check during the 14 days that the account still works: a changed password locks every tester out.
What Peerbeta does
When at least two testers report being stuck at sign-in and the test gives no test account, the diagnosis warns you.
Was this helpful?
Your feedback shapes what we write next.
Related articles
Connect the tester app to your accountSign in to the tester app with Google, or with the 8-character pairing code shown in your tester space on the web. A code works once, for 10 minutes.Step 5: check the target API levelGoogle refuses a new app that targets too old an API: since 31 August 2026, API 36 for phone apps. Check targetSdk in build.gradle and enter it in Peerbeta.Step 3: take our testers off internal testingA tester enrolled in your app's internal testing doesn't get the closed test. Remove our group, and any list with our testers, from “Internal testing › Testers”.Step 6: publish the closed testing trackThe opt-in link only exists once the track is published. Upload your AAB, roll the release out to the track, send it for review and wait for “Published”.