Play Console setup

J

By Jordan·8 articles

Testers are stuck at the app's sign-in screenThe 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”.

Step 2: add the testers' group to the trackPeerbeta's testers reach your app through our Google group. In the track's “Testers” tab, choose “Google Groups” and paste our address.

Step 4: choose the track's countriesTesters count by the country of their Google Play account. In the track's “Countries/regions” tab, add every country and region, or at least the test's countries.

Step 7: copy the opt-in link and paste it in PeerbetaIn the published track's “Testers” tab, copy the “Join on the web” link, which starts with https://play.google.com/apps/testing/, and paste it in Peerbeta.

Step 1: create the closed testing trackThe test runs on a closed testing track of your app in the Play Console. Open “Test and release › Testing › Closed testing” and keep one track for the whole test.

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”.

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 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.