Troubleshooting

Testers Cannot Install the App From the Closed Test

Why testers see 'not available' or install errors on the closed test page, and how to fix it.

Reviewed August 17, 2026May change — always verify in Play Console1 official source

Written & maintained by AppsTestLabAbout AppsTestLabHow we research

On this page
  1. Why it happens
  2. The quick fix
  3. Step by step
  4. Things to check
  5. If this didn't work
  6. Common mistakes
  7. When to contact Google

The problem

Testers click the opt-in link or see the app page, but installation fails with 'not available' or a store error.

Why it happens

Most install problems trace back to eligibility: the tester hasn't opted in with the correct Google Account, wasn't actually added to the closed track's list or group, or the release hasn't finished its review. Device and region eligibility can also block the install.

The quick fix

Ask the tester to open the opt-in link signed into the same Google Account that's on your tester list, tap 'Become a tester', then install from the Play Store page that opens.

Step by step

  1. Confirm the tester is on the list

    In Play Console, open the track's Testers tab and confirm the exact Google Account email is in the list or in the linked Google Group.

  2. Check the Google Account in use

    The tester must be signed into the same account on the phone and in the browser where they open the opt-in link.

  3. Reorder the steps

    The tester should tap Become a tester first, wait for the confirmation, then install from the app's Play Store page. Installing before opting in fails.

  4. Check release and device eligibility

    Verify the release is published to the track and the tester's device meets the app's minimum requirements.

Things to check

  • Exact email on the tester list
  • Google Group membership
  • Tester opted in before installing
  • Release published status
  • Device Android version and region

If this didn't work

  • Have the tester try on another device or sign out of a secondary Google Account on the phone.
  • Re-check region availability for the test track on the track's availability settings.

Common mistakes

  • Adding a work email to the list but asking testers to use a personal Google Account
  • Skipping the opt-in step and going straight to the store page
  • Sharing the link before the release finished review

When to contact Google

Contact Play Console support through Help & feedback if a verified tester on a published release still cannot install after trying these steps.

Sources & references

Official Google documentation

These links open Google's official Play Console Help pages used to verify this guide. AppsTestLab guidance is independent and not affiliated with Google.

Last reviewed August 17, 2026 · Google Play requirements change — verify in the Play Console.

Ready to test?

5,000+ apps tested. A 99% historical approval rate. And a 100% money-back guarantee.

Tell us about your app and we'll confirm the right testing approach. One WhatsApp message to start, no complicated setup.

Guarantee applies to eligible app testing orders · Google makes the final approval decision

Chat on WhatsApp