A closed test is not on the public Play Store, so searching for it will never find it. Your tester has to open your opt-in link, accept it, and only then can they install the app.
If they have done that and still see nothing, it is almost always one of six things. Five of them take a minute to fix.
Below is every cause and the fix, so you can sort this out today. It is also worth saying plainly: this whole page describes work you only do if you are recruiting testers yourself. When you opt for Testers Community, you send us the app and the opt-in link, and none of this reaches you.
Updated September 2026
What your tester should see
Three screens, in this order.
- Your message, containing the opt-in link you copied from Play Console.
- The opt-in page, where they accept and become a tester.
- The Play Store page for your app, with an Install button.
Miss the middle screen and the third one never works. Accepting the invite is the step people skip, because it looks like a notice rather than a task.
This is one you only deal with when you recruit testers yourself. Our testers have done it hundreds of times, so it never comes up.
Why searching the Play Store finds nothing
Because your app is not public yet.
A closed test is private to the people on your list. There is no public listing to find. Telling a tester to search the Play Store sends them looking for something that is not there.
Always send the link. Never send the app name.
The six reasons a tester cannot see your app
The first three cause nearly all of it. Work down the list in order.
| What is happening | The fix |
|---|---|
| Their email is not on your tester list at all | Open your closed testing track, go to Testers, and add the exact address they use on their phone |
| They are signed in with a different Google account | The address on your list must be the account signed in on their phone |
| Their country is not on your track | Add their country under Countries and regions on the closed testing track |
| They never accepted the invite | Send the opt-in link again and ask them to tap accept on that page |
| You only just published the test | Wait. Google says the test link can take several hours to reach testers [1] |
| You changed the release just now | Changes also take several hours to reach testers [1] |
Start here: is their email actually on the list?
This is the most common cause, and the easiest to overlook.
A tester can only see your app if their Google account is on the tester list for that track. Not the release notes, not a message from you, the list itself.
Open Test and release > Testing > Closed testing, open your track, and check the Testers tab. If the address is missing, add it, save, and send them the opt-in link again.
The account mix-up, explained
This is the most common one, and it is easy to miss.
Plenty of people have two Google accounts on one phone, a personal one and a work one. Say you invited the work address, but their Play Store is signed in as the personal one. The app will not appear, and nothing will look wrong.
Ask your tester to open the Play Store, tap their profile picture, and read the email address shown. It has to match the address on your tester list exactly.
Before you blame anything, check the clock
Google says the test link can take several hours to become available to testers after you first publish a test. Later changes can take several hours too [1].
If you published this morning and your tester is looking now, there may be nothing wrong at all. Give it a few hours before changing anything.
What to send your tester
One message, with everything in it, saves most of this trouble.
- The opt-in link on its own line, so it is easy to tap.
- The exact email address they must be signed in with.
- A warning that they are not finished until the opt-in page confirms it.
- A note not to search the Play Store, because the app is not public.
Our post on how to invite testers properly has the wording, and can my testers be in different countries covers the country setting.
Frequently asked questions
Why can my tester not find my app on the Play Store?
Because a closed test is private. The app has no public listing, so searching will not find it. Your tester reaches it through your opt-in link, and only after they accept the invite on that page.
How long does it take for a tester to see the app?
Google says the test link can take several hours to reach testers after you first publish a test. Changes can take several hours as well.
My tester accepted the invite but still cannot install. Why?
Usually the account. The Google account signed in on their phone has to be the same address you added to the tester list. Two accounts on one phone is the usual cause.
Why can my tester not see the app even though I sent the link?
Check that their email address is actually on the tester list for the closed testing track. The link alone does nothing if the account is not on the list.
Does my tester need to be in a particular country?
They need to be in a country you selected for the closed testing track. If their country is not on the list, the app will not be available to them.
Should I send the app name or the link?
Always the link. The app name is useless during a closed test, because there is nothing public to search for.
What this looks like when we run it
Short version: you send the opt-in link, and we take it from there.
We assign verified testers on real Android devices, and they already know the opt-in step, so nobody needs it explained. They stay for the full 14 days, and if anyone goes quiet we replace them.
Accounts and countries are sorted before testing starts, which is the cause of most of the trouble on this page. At the end you get a feedback report, so you are not guessing whether anyone opened the app, and we help you write the production access answers.
Two things stay with you, and we will not pretend otherwise. You submit the application yourself, and Google makes the decision. If it is refused, you get your money back.
Send us the link and stop chasing people
Option 1: verified testers assigned to you
- Starter, $15 gives you 15 verified Android testers for the full 14 days.
- Pro, $25 gives you 25 testers, plus a detailed ASO report and priority support.
- Testers opt in within 6 hours, so your 14 days start today.
- Verified real Android devices, never emulators.
- Full 14-day retention. They keep using your app for the whole test.
- Automatic tester replacement if anyone goes quiet.
- A feedback report at the end, plus help with the production access questions.
- Production-access guarantee. Approved, or your money back.
This is what we do, and we are the best at it. We have been helping developers through Google Play closed testing since March 2024, longer than most services in this category. Opt for a plan when you are ready.
Option 2: join a free Pack of 16
The Testers Community app puts you in a group of 16 developers who test each other’s apps for 16 days. Anyone who stops testing is replaced.
If the count is your problem rather than one tester, see why it says 0 testers currently opted in.
