Check the Closed-Test Opt-In Link

How to confirm before you submit an application that your closed-test opt-in link opens on the right track and package, and that opting in actually leads to an install.

Check what the opt-in link is

The opt-in link is shown on the testers tab of the closed track in Play Console. It is a different address from the app's store listing, and each track gets its own.

Enter that opt-in link in the application, not the store address. If you have several tracks, confirm it is the link for the track the test accounts are actually registered on. Which track accounts go on is covered in add tester emails to your closed track.

Check the package name matches the app you applied with

Confirm the package name in the opt-in link is the same as the package name in your application. When a development build and a release build carry different package names, the link opens normally but the app actually being operated is a different one.

The same package name is shown on the app detail screen in the workspace, so you can compare it once more after applying.

Opening is not the same as installing

An opt-in screen that opens does not mean the app can be installed. Opt in, follow through to the store, and check that an install button appears.

If the opt-in screen opens but the install does not, check in order whether the account is on the tester list, whether the track has a published release, and whether the account's country is included in the app's availability. Recording which of the install and launch steps it stopped at is covered in recording a launch failure separately from Crash and ANR.

Check with an account you do not use for testing

Checking from your own developer account can show a different result from a real tester's, because you already have access to the app.

Where possible, open the link from an account that is not registered on the track to see what appears, and separately confirm that a registered account gets all the way to an install. If the two results differ, the problem is the tester registration state rather than the link.

Checklist before you submit

Confirm that the link's track is the track the accounts are registered on, that the link's package name matches the app you applied with, that the track has a published release, and that South Korea is included in the app's country availability. When all four hold, the readiness check usually passes as it is.

The minimum of 12 testers and the continuous 14 days that the application itself is measured against are worth reading alongside this, in the 12 testers for 14 days checklist. If you are still comparing managed services, start with choosing a Google Play closed testing service. If you get stuck, tell us through support what the screen said.