Setting up closed testing

Before you start

• A Play Console developer account (the one-off registration fee is paid).
• A signed Android App Bundle (.aab) — Play no longer accepts APKs for new apps. In Android Studio: Build → Generate Signed App Bundle.
• Your app's package name (the applicationId in your module's build.gradle). It can never change after your first upload.

1. Create the app

1. In Play Console, go to All apps → Create app.
2. Set the app name, default language, and whether it's an app or a game, free or paid. Free vs paid can't be changed later once published.
3. Accept the declarations and create.

2. Set up the closed testing track

1. Go to Test and release → Testing → Closed testing.
2. Play gives you a default track (often called "Alpha"). Either use it or select Create track for your own.
3. Select Create new release on that track.
4. Let Play manage your signing key (Play App Signing) unless you have a strong reason not to, then upload your .aab.
5. Add a release name and release notes, then Next → Save.

Don't roll out yet if your testers aren't added — but note the track must actually be rolled out (not left as a draft) before anyone can opt in and install.

3. Add your testers

This is the step that determines whether the 14-day clock starts.

1. On your closed track, open the Testers tab.
2. Choose Create email list (or reuse an existing list), give it a name, and paste in the tester Google account addresses — comma-separated works.
3. Tick the list so it's applied to this track, then Save changes.

If you're using App Test Bench, this is where our device accounts go. Submit your app in the dashboard and we'll show you the exact list to paste, with a copy button.

4. Complete the app content declarations

Play won't let a release reach testers until the app's paperwork is done. Under Policy and programmes → App content you'll need at minimum:

• Privacy policy URL
• Ads declaration
• App access (login details if any screens are behind a sign-in)
• Content rating questionnaire
• Target audience and content
• Data safety form

Fill these in honestly and completely now. They're also what production review checks, so getting them right today saves a rejection in two weeks.

5. Roll out

Back on the release, select Review release → Start rollout to Closed testing. Play reviews the build first — this usually takes hours but can take days for a brand new account. Once it's live, your testers can opt in.

Next: find your opt-in link and submit your app.