Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Flutter and app store releases

Testers cannot find or install the app from Play internal testing

ErrorInternal testers cannot find the app when they search Google Play

Short answer

An internal test is not searchable on Google Play. Testers install only through the opt-in link, and only after the app status is Published and their email is on a tester list you selected for the release. Each tester must open the link and opt in. After a first publish, allow a few hours for the link to work.

  • Applies to Play Console internal testing, Google Play Store app
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Open Test and release, Testing, Internal testing and look at two things: the app status and the Testers tab. The checks below follow from what you see there.

    # Play Console: Test and release > Testing > Internal testing > Testers
  2. 2Match what you see, then jump to its fix

    1. 1The tester says the app does not appear in searchThe tester searched Google Play instead of using the linkFix
    2. 2No opt-in link shown for the track, or the link does not work after the first uploadThe app status is not Published yetFix
    3. 3The tester cannot install even with the linkThe tester is not on a selected list, or has not opted inFix
    4. 4The same person was invited to closed or open testingThe tester is already in another testing trackFix

What does the error look like?

  • Internal testers cannot find the app when they search Google Play
  • The opt-in link is missing in Play Console for the internal test

Cause 1 of 4

The tester searched Google Play instead of using the link

1Check

Internal test apps are not listed in search results. The release is shared by URL only.

# Copy the link from the Testers tab of Internal testing

2Fix

Copy the shareable link on the Testers tab, save changes, and send that link to each tester.

# Testers tab > Copy link > Save changes

3Verify

The tester opens the link on a device signed in with an address from the list.

# Tester: open link, read the responsibilities page, opt in

Confirmed by support.google.com

Did this fix it?

Cause 2 of 4

The app status is not Published yet

1Check

The opt-in link appears only when the app status is Published. Draft or pending publication apps show none. After the first publish and later changes, it can take several hours to start working.

# Play Console: Publishing overview, look for unsent changes

2Fix

Finish the required setup, send the pending changes for review, and wait for the release to go live.

# Publishing overview > Send changes for review

3Verify

The Internal testing page shows the link and the release is marked available.

# Internal testing > Testers tab

Confirmed by support.google.com

Did this fix it?

Cause 3 of 4

The tester is not on a selected list, or has not opted in

1Check

Testers need a Google Account address that is on a list selected for the release, and each tester must opt in with the link. Lists accept up to 100 testers per app. A CSV must have one address per line, no commas, and not be UTF-8 with BOM.

# Testers tab: tick the list, check each address

2Fix

Add the address to a list, tick that list in the Testers table, then save. Ask the tester to open the link and accept.

# Add emails or Upload CSV file > select list > Save changes

3Verify

The tester can install from the link.

# Tester: install via Play Store from the link

Confirmed by support.google.com

Did this fix it?

Cause 4 of 4

The tester is already in another testing track

1Check

A user who opted into internal testing is not eligible for open or closed testing. They must opt out of internal testing first.

# Ask the tester which test link they accepted

2Fix

Have the tester opt out of internal testing first, then join the track you want.

# Tester: opt out of the internal test, then use the other link

3Verify

The tester opens the other opt-in link and can join.

# Tester: reopen the link

Confirmed by support.google.com

Did this fix it?

How do I stop it coming back?

  • Send testers the opt-in link, not the app name.
  • Create one tester list for the team and tick it on every release.
  • Publish the first internal release a day before the demo.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Projects of mine built on the same technologies:

Related fixes

Mobile apps

Android Studio cannot pair the phone over Wi-Fi

The Pair devices over Wi-Fi dialog lists no device

Wireless pairing needs the phone on Android 11 or higher and on the same Wi-Fi network as the computer, with current Platform-Tools.

4 causes, each with a fix

Mobile apps

adb tcpip 5555 fails because no device is found

adb: more than one device/emulator

adb tcpip only works while the device is attached and listed by adb, because it tells the phone to start listening on port 5555.

4 causes, each with a fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.