Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My testers cannot find the app in Google Play internal testing

Short answer

Google does not list internal-test apps in Play search. Testers need the opt-in link, which Play Console shows only once the app is Published, and they must be on a tester list you selected. Each tester opens the link and opts in. After a first publish, the link can take hours to work.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • Testers search Google Play and find nothing.
  • I cannot find the opt-in link in Play Console.
  • The link opens and says the app is not available.
  • Some testers see the app and others do not.
  • The test was working yesterday and now it is not.

Why does this happen?

  1. Internal tests cannot be found by searching

    Google says testers cannot find the app by searching during an internal test. You have to share the Play Store link or the opt-in link.

  2. The app is not Published yet

    The opt-in link appears only when the app status is Published. Apps in Draft or Pending publication do not show one.

  3. The tester is not on the list or has not opted in

    Testers are added by email address from a list that you select for the test. Each tester must also open the link and opt in individually.

  4. It takes a while after the first publish

    Google says a test link can take several hours to become available after the first publish, and changes later can also take several hours.

  5. The tester is already in another test

    A user opted into internal testing is not eligible for open or closed tests until they opt out of the internal test. Testers also need a Google Account or a Google Workspace account.

What can I do about it today?

  1. Send the link, not instructions to searchCopy the shareable link from the Testers tab and send it to each tester.
  2. Check the app statusIn Play Console see whether the app is Published or still pending changes.
  3. Check the tester listConfirm that the email address a tester uses on their phone is on the selected list.
  4. Ask the tester to open the link on their phoneThey must be signed in to the same Google account that is on the list.
  5. Wait a few hours after the first publishDo not recreate the test in the meantime. Repeated changes make it harder to tell what works.

When should I bring someone in?

  • Everything above is correct and testers still cannot install.
  • You cannot reach Play Console or your role does not show Testing.
  • Your release depends on testers confirming a fix.

How do I handle it?

  1. Follow the opt-in pathI check the app status, release, tester list and link in that order.
  2. Find the breakEach point in the path has a clear sign, so the failing one is found quickly.
  3. Test with a fresh accountA test with a new tester shows what real testers see.
  4. Prepare the next stepIf the app is ready for wider testing, I explain which test track comes next.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

How many internal testers can there be?

Google states up to 100 testers per app.

Does the tester pay for the app?

Google says testers can install paid apps for free, but pay for in-app purchases unless they are on a license testers list.

Can testers leave public reviews?

Google says they cannot leave public reviews on test versions, so give them another feedback channel.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.