Overview

For newer personal Play Console accounts, Google requires a closed test before production access.

The clean setup is: create a Google Group, add it to a closed testing track, release your app, then share three links in order.

Closed testing flow

Set up once, then share three links

Your testers need to join the group, opt in on Google Play, and install the app with the same Google account.

1 Join Google Group Gives access to the test 2 Become a tester Opt in on Google Play 3 Install app Keep the test active

What Google asks for

For personal developer accounts created after November 13, 2023, Google says you need at least 12 testers opted in to a closed test for 14 continuous days before you can apply for production access.

Official references:

Before you start

Step 1: Create a Google Group

Open Google Groups and create a group for your testers. Google’s guide is here: Create a group and choose group settings.

Use a simple name, such as:

your-app-testers@googlegroups.com

Set the group so testers can join from the group link. The exact labels may change, but check these:

  • Testers can open the group link.
  • Testers can join, or request to join if you want approval.
  • You can copy the group email.

Google’s tester-side guide may help if someone is new to Groups: Find and join a group.

Step 2: Set up closed testing

In Play Console, open:

Test and release > Testing > Closed testing

Use the default closed testing track, or create one with a clear name:

first-closed-test

In the Testers tab, choose Google Groups and add your group email:

your-app-testers@googlegroups.com

Add your feedback email or URL, then save. Google’s closed testing guide is here: Set up an open, closed, or internal test.

Step 3: Release to closed testing

Upload your Android App Bundle to the closed testing track. Fill in the release notes and start the review.

After the quick check finishes, Play Console does not send the release on its own. Press Send changes for review. The button may say Send 1 change for review or Send 2 changes for review.

The track overview can show the new version number even before you press it, so it looks finished when it is not. Until you send the changes, testers may see “app not available”.

Wait until the release is reviewed and available before sending testers the links.

If you also use an internal testing track, update that too, or leave it. Internal testing is served first, so a stale internal build can hide the closed test on your own phone.

Google’s release guide is here: Prepare and roll out a release.

Send these in order:

  1. Google Group link
    This lets testers join the group.

  2. Become a tester link
    This is the opt-in link from Play Console.

  3. Install app link
    This is the Play Store app link.

Ask testers to use the same Google account for all three steps.

Message to send

You can copy this and replace the links. Dearly’s Android tester guide is a live example of the page you can share with testers.

I am running a closed test for my Android app before publishing it on Google Play.

Full steps: https://www.trydearly.com/android-tester-guide

Please use the same Google account for each step:

1. Join this Google Group: [group link]
2. Become a tester: [tester opt-in link]
3. Install the app: [Play Store link]

Please stay opted in for 14 days. Short, honest feedback is enough.

Keep the test honest

Ask testers to install the app, try the main flow, and tell you what feels broken or unclear.

You do not need fake daily tasks. You do need real feedback. Keep a few notes for your production access form:

  • How you found testers.
  • What they tested.
  • What feedback came in.
  • What you changed or plan to change.

After 14 days

Once at least 12 testers have stayed opted in for 14 continuous days, apply for production access from the Play Console dashboard.

Google may ask what feedback you received and how you improved the app during testing. Do not leave this until the last day. Ask testers for honest notes, fix the useful issues, and make a few closed testing releases as the app improves.

Good examples to save:

  • Confusing screens or flows testers pointed out.
  • Bugs, crashes, or install issues you fixed.
  • Small improvements shipped in later test releases.

Common problems

Do testers need to open the app every day?

Google’s stated requirement is continuous opt-in for 14 days. Ask testers to genuinely try the app and share feedback, but do not turn testing into fake daily check-ins.

Testers see “item not found”

They may have opened the install link too early, used the wrong Google account, or tried before the release was available.

Testers see “app not available”

The track overview can show the new version even if you have not sent it for review. After the quick check, press Send changes for review. Until then, testers can get “app not available”.

Your own phone will not update

Internal testing is served before closed testing. If your account is also in an internal test and that build is older, Play keeps giving you the internal one.

Leave the internal test, or release the same version there, then try again.

Testers joined the group but cannot install

They still need to open the tester opt-in link.

Testers used the wrong Google account

Use the same account for:

  • Google Group membership.
  • Tester opt-in.
  • Play Store install.

Wait a few hours. Test links and release changes can take time to become available.

A tester opts out before 14 days

That tester may stop counting. The 14 days need to be continuous.

What you do not need

You do not need to pay a tester marketplace just to create a closed testing track.

Some sites make this sound harder than it is because they sell access to testers. Paid help may be useful for some teams, but it is not required for the basic setup.

The official flow is enough: group, closed test, release, three links, 12 real testers for 14 continuous days.

Quick checklist