Reachability check · why the app is not showing up
If any one of these five relays is off, the opt-in link lands on "App not available" on your tester's phone. Tap a relay to jump straight to its fix, or read them in order below.
Quick Answer
In 99% of cases, your closed testing has not started because your app is not yet available to your testers on Google Play. The five most common causes are: a track mismatch between the release and the tester list, an unselected tester list (uploaded but checkbox not ticked), the wrong link copied (internal vs closed), restricted countries, or changes still pending Google review. All five are fixable in Play Console in under 30 minutes - or you can skip the hassle entirely by using PrimeTestLab, which provides 12 to 25 pre-vetted real testers and starts your 14-day cycle within 4-6 hours.
If you set up a closed test on Google Play and your testers tell you the app is "not available" or "not found," do not panic. This is one of the most common pre-launch issues, and it almost always traces back to one of five Play Console settings. This guide walks through each cause, shows you exactly what to fix, and explains why your testers cannot see the app even when everything "looks right." If you need real testers fast, PrimeTestLab provides 12 to 25 vetted testers starting at $19.99 with testing typically beginning within 4-6 hours once your app is reachable.
What This Post Covers
Watch the 5-Minute Video Walkthrough
Step-by-step tour of the Play Console settings to check
The 5 Most Common Reasons Closed Testing Is Not Starting
Before diving into each fix, here is the short version. Skim these five and you will recognize the one that applies to your project. We have helped 7,400+ apps through closed testing, and the same handful of issues show up over and over.
Release and tester list are on different tracks
You published a release on one track but attached the tester list to a different track. Testers see nothing.
Blocked 2Tester list is uploaded but the checkbox is not ticked
The most missed setting. The list shows in the table, but it is not actually active for the track.
Blocked 3You copied the internal testing link, not the closed testing link
Internal and closed testing are separate tracks. Sharing the wrong link means your testers join the wrong test (or none at all).
Blocked 4Country restrictions are blocking your testers
Selecting only 2 or 3 countries blocks testers from other regions. Closed testing countries are independent of your production release.
Blocked 5Changes are still pending Google review
New tester lists and country changes need Google approval. Without clicking "Send changes for review," your changes never go live.
BlockedGood news: all five fixes are inside Google Play Console - no developer account changes, no app rebuild, no policy appeals. Most users are back on track in under 30 minutes.
Reason 1: Your Release and Tester List Are on Different Tracks
Google Play Console lets you create multiple closed testing tracks. Each track has its own release and its own tester list. A common mistake is to publish the release on Track A but add testers to Track B. The two never meet, and your testers see nothing.
Click to enlarge
How to Check It
- Open Testing > Closed testing in Play Console.
- Identify the active track that has a release. Click Manage track.
- Confirm the release status reads Available to selected testers (not "In draft" or "Halted").
- Switch to the Testers sub-page on that same track. Your tester list must be attached here, not on a different track.
Wrong
Release published on Track A, tester list attached to Track B. Result: testers cannot see anything because the track they joined has no release.
Right
Release Active on Track A, tester list attached to Track A, status shows "Available to selected testers" with the correct version number.
If Your Release Is Still in Draft
If the track shows "Edit draft" instead of an active release, you have a release in progress but not yet published. Click into the draft, complete the release notes, and click Save and publish. If there is no release at all, click Create new release and roll one out to that track.
Pro Tip
If you only need one closed test, keep things simple - use a single track. Multiple tracks are useful for staged rollouts (alpha team, beta team, customers) but are a frequent cause of "where did my testers go?" confusion.
Reason 2: Your Tester List Is Uploaded But the Checkbox Is Not Ticked
This is the silent killer. Most users upload the CSV correctly, save the list, and assume Play Console "knows" to use it. But Google requires one extra step: you must tick the checkbox next to the list to actually select it for the track. Without that tick, the list shows up in the lists table but is not active.
Click to enlarge
The Exact Steps
Upload the CSV
In Manage track > Testers, click Create email list, upload your CSV file, and give the list a name (any name - "PrimeTestLab Testers", "Friends", "Beta Cohort 1"). Click Save changes.
Tick the checkbox next to your list
The new list appears in the lists table. Tick the checkbox to its left. Without this tick, the list exists but is not active for the track. This single step is the #1 cause of "my testers cannot see the app."
Click Save (again)
After ticking the checkbox, click Save at the bottom of the page. You should see a confirmation toast and the list status should change to "Selected for this track."
Why This Bug Exists
Google Play Console treats "creating a list" and "selecting a list for a track" as two separate operations. This means you can have many lists in your account but only specific ones active per track. It is by design - but the UI does not warn you, so it is easy to assume the upload is enough. It is not.
Reason 3: You Copied the Internal Testing Link Instead of the Closed Testing Link
Google Play has three distinct testing tracks: Internal, Closed, and Open. Each one generates its own opt-in link. If you accidentally copy the internal testing link and share it with your closed testing testers, they will be redirected to the internal track - which they are not invited to. The result: "App not available."
Internal testing is intended for up to 100 trusted teammates inside your organization. It does not count toward Google's 14-day production access requirement. Only closed testing time counts.
Click to enlarge
How to Tell Which Link Is Which
| Where Copied From | Track | Counts Toward 14 Days? |
|---|---|---|
| Testing > Internal testing | Internal (up to 100 testers) | No |
| Testing > Closed testing | Closed (the one you need) | Yes |
| Testing > Open testing | Open (public beta) | Yes (different rules) |
Spot-Check the URL Itself
Google Play opt-in URLs include the track type in the path. Look at the URL you are about to share:
- Internal track:
play.google.com/apps/internaltest/...- Wrong for closed testing - Closed testing opt-in:
play.google.com/apps/testing/<package>- Correct (testers tap this to join your test) - Play Store listing:
play.google.com/store/apps/details?id=<package>- Also valid (testers install from here after opting in)
Validate Your Closed Testing Link
Paste your Play Console opt-in URL to instantly check if it is the correct closed testing link.
Quick Fix
Always copy the link directly from the Closed testing > Manage track page. Do not save links from previous projects, do not paste from old documentation, and do not assume "Internal testing" is "sort of the same thing." It is a separate track, and it does not count.
For a deeper comparison of the three testing tracks, see our guide on Internal vs Closed vs Open Testing.
Reason 4: Country Restrictions Are Blocking Your Testers
When you set up a closed test, Play Console asks you to choose which countries can access the app. Many developers select only 2 or 3 countries (their own + maybe one nearby) and then wonder why testers from other regions cannot install. Real testers - whether from PrimeTestLab or your own network - come from many countries, and a tight whitelist will silently block most of them.
Click to enlarge
Important Distinction
Closed testing country settings are completely separate from your production release. You can target the entire world for closed testing, then restrict to specific countries on production - or vice versa. The two settings live on different pages and do not influence each other.
The Recommendation
Best: All 177
Select every available country. Maximum tester reach, zero gating.
Minimum: US + Local + ROW
United States, your country, and "Rest of the world." Anything tighter and you risk blocking testers.
Paid Apps
Some countries are unavailable for paid apps - select all that ARE available.
How to Fix It
- Open Testing > Closed testing > Manage track.
- Click Countries / regions.
- Click Select all, or manually select a wide list.
- Click Save. The change becomes a "pending change" until you submit it on the Publishing overview page (covered in the next section).
Common Concern
"I am only launching in one country - why select all 177?" Because closed testing is internal-only. The opt-in link is invite-only and never shows up to the public. Selecting all countries here does not affect who can find or download your app at launch.
Reason 5: You Forgot to Click "Send Changes for Review"
This is the final, deceptively simple step that catches almost everyone. Anything you change in Play Console - new tester lists, country settings, releases, store listing tweaks - sits in a pending state until you submit the batch to Google for review. Without that click, every other step you took is invisible to your testers.
Click to enlarge
Where to Find It
- In the left sidebar of Play Console, find Publishing overview.
- You will see a list of pending changes - the new tester list, the country selection, the release, etc.
- Click the blue Send changes for review button at the top of the page.
- Wait for Google approval. The status badge will change from "Pending" to "Approved" once Google clears it.
Approval timing: typically 20 to 30 minutes, occasionally a few hours. As soon as Google approves, your testers can install the app and your 14-day window can begin.
What "Pending Review" Looks Like
Pending
Yellow "Pending" badges next to each change. The tester list, countries, or release will not be live until reviewed and approved by Google.
Approved
Green "Approved" badges and the changes are now visible to your testers. Time to share the closed testing opt-in link.
Sanity Check
After approval, open the closed testing opt-in link on a phone you are not signed into Play Console with. If it loads, your test is genuinely live. If it shows "App not available," return to the previous reasons - one of them is still wrong.
Pre-Flight Checklist Before You Tell Anyone Testing Is Ready
Once you have applied the fixes above, run through this checklist before you share the opt-in link with your testers (or before you submit your link to PrimeTestLab). Each item maps to one of the five issues - if all five tick, your closed testing is genuinely ready.
-
The release is Active on a closed testing track
Open the track. The status reads "Available to selected testers" with a real version number, not "Draft" or "Halted."
-
The tester list is uploaded AND its checkbox is ticked
Both - upload alone is not enough. The list status on the track must show "Selected."
-
The opt-in link comes from "Closed testing" (not Internal)
The URL contains
play.google.com/apps/testing/notinternaltest. -
Countries are unrestricted (or include all relevant regions)
Ideally all 177 countries are selected. At minimum, your testers' countries plus the United States plus Rest of world.
-
Publishing overview shows zero pending changes
Either everything is approved (green) or there is nothing waiting. If anything is yellow/pending, click Send changes for review and wait for approval.
-
You opened the link in a logged-out or different account
Best smoke test: open the closed testing URL in a browser you are not signed into Play Console with. If the opt-in page loads, your test is genuinely available.
The Bottom Line
If all six items tick, your closed testing is genuinely ready. Testers can install. The 14-day clock can start. If anything is still failing, it is almost always one of the five reasons above - go back and recheck that specific item.
How PrimeTestLab Helps You Skip the "Cannot See Your App" Phase
If your real challenge is "I do not know any 12+ Android testers willing to keep an app installed for 14 days," that is exactly what PrimeTestLab exists for. We provide pre-vetted testers, walk you through the Play Console setup so you do not hit the five issues above, and start testing as soon as your app is reachable from our test devices.
Current Packages
- Meets Google's minimum
- Real Android devices
- Full 14-day coverage
- Maximum safety margin
- Best device diversity
- Strongest first-attempt rate
- Safety buffer included
- Better device diversity
- Higher approval confidence
Why More Than 12
12 testers is the bare Google minimum. If even one tester drops below the minimum during the 14 days, the timer can reset. Most developers go with 20 to 25 testers as a safety margin so a single drop-off does not erase 14 days of progress.
Helpful Links
Frequently Asked Questions
Why is my Google Play closed testing not starting?
In 99% of cases, your closed testing has not started because the app is not yet available to your testers. The five most common causes are: the release and the tester list are on different tracks, the tester list was uploaded but the checkbox was not ticked, you copied the internal testing link instead of the closed testing link, country restrictions are blocking your testers, or you forgot to click Send changes for review on the Publishing overview page.
How long does Google take to approve closed testing changes?
Google's review of closed testing changes typically takes 20 to 30 minutes, but can occasionally take a few hours depending on Google's queue and the type of changes submitted. After approval, your testers can install the app immediately and the 14-day testing window can begin.
Why can my testers not see my app even though I added them?
The most common reason is that you uploaded the tester list as a CSV but did not tick the checkbox to actually select that list for the closed testing track. The list shows in the table but is not active. The other common cause is that the release and the tester list are on different tracks - for example, the release is published on Track A but the tester list is attached to Track B.
Is there a difference between internal testing and closed testing links?
Yes, they are completely different. Internal testing is meant for up to 100 testers within your organization and does not count toward Google's 14-day production access requirement. Closed testing is the track required for production access on personal accounts. Always copy the link from the Closed testing page in Play Console, not the Internal testing page.
Do I really need to select all 177 countries for closed testing?
Selecting all 177 countries is the safest option because testers come from many regions. Country restrictions on closed testing are completely separate from your production release - you can target any countries you want on production after closed testing is approved. At minimum, select the United States, the country your testers live in, and the Rest of the world option.
What is the "Send changes for review" button on Publishing overview?
Anything you change in Play Console - new tester lists, country settings, or releases - sits in a pending state until you submit it via the Publishing overview page. Click Send changes for review to push the changes to Google. Without this step, your testers will not be able to install the app even if every other setting is correct.
How fast can PrimeTestLab help start closed testing?
Once your app is visible to PrimeTestLab testers in Play Console, testing typically begins within 4-6 hours. Starter pricing starts at $19.99 for 12 testers.
Bottom Line
Summary
If your closed testing has not started, the app is almost certainly not yet available to your testers because of one of five fixable Play Console issues: a track mismatch, an unselected tester list, the wrong opt-in link, restrictive country settings, or pending changes that were never submitted to Google for review. All five live in your Play Console - no developer account changes, no rebuilds, no policy appeals. Run the pre-flight checklist above, click Send changes for review, wait 20 to 30 minutes, and you should be live. If you still need real testers to actually run the 14-day cycle, PrimeTestLab provides 12 to 25 vetted testers starting at $19.99 with testing typically beginning in 4-6 hours. See pricing plans →