If your app shows as published in Google Play Console but is not appearing in the store, the most common reasons are a search indexing delay right after publishing, and device compatibility filtering that hides the app from devices or accounts that do not meet its declared requirements. Confirm the app is actually live by opening its direct store URL; if that page loads, the app is published and the issue is discovery, not publishing. A newly published app can take a few hours to become searchable, and it will never appear in search or browse on a device it is not compatible with.
Short answer
A published app that is not in the store is usually a discovery problem, not a publishing failure. Per Google's Play Console Help, a newly published app is live at its direct URL first and becomes searchable after Google indexes it, which takes a few hours. Separately, per Android's device compatibility rules, the app only appears for devices that meet its declared requirements, so an incompatible device will not see it in search or browse. Check the direct store URL to confirm it is live, wait for indexing, and verify the searching device is compatible and in a covered country.
Where to look first
The first thing to check is whether the app is actually live, which you confirm by opening its direct Play Store URL rather than searching for it. If the store listing page loads, the app is published and available, and the problem is that people are not finding it, not that it failed to publish. If the direct URL also fails, the release is not live yet, and you should look at review status, rollout, and Managed Publishing instead.
Making that distinction first saves time, because a live-but-not-searchable app and a not-yet-published app have completely different fixes. Once you know the app is live at its URL, the causes narrow to indexing time, device compatibility, country availability, and staged rollout. If it is not live at the URL, the causes are on the publishing side. Everything below assumes you have checked the direct URL and know which case you are in.
Is it an indexing delay?
Yes, an indexing delay is the most common reason a freshly published app is live but not showing in search. When you publish, the app becomes available at its direct store URL first, and Google then needs time to index the listing before it appears in search results and browse. That indexing typically takes a few hours, so searching for your app in the minutes after publishing will often turn up nothing even though the app is fully live.
The practical step is to confirm the app loads at its direct URL, then wait a few hours and search again. Do not assume publishing failed just because search does not find the app immediately. If the direct URL works but search still does not surface the app well beyond a few hours, look next at device compatibility and the search terms you are using, since an exact-title search from a compatible device is the most reliable way to find a newly indexed listing.
Device compatibility filtering
Device compatibility filtering is the other leading cause, and it is easy to miss because the app is genuinely live. Google Play only shows an app to devices that meet its declared requirements, so an app that requires a feature, a minimum Android version, or hardware the searching device lacks will not appear in search or browse on that device. If you test from a device that does not meet the requirements, you will not find the app even though other users can.
The declared requirements come from your manifest, including uses-feature entries marked required, the minimum SDK version, and supported screen or hardware declarations, plus the device catalog exclusions in Play Console. Review these against the device you are searching from, and check the device catalog to see which devices your app supports. To confirm the app is live independent of compatibility, open the direct URL, and to test discovery properly, search from a device that meets every declared requirement.
Country and rollout
Country availability and staged rollout also hide a live app from specific users. If the app is not available in a country, users there will not see it in the store, so confirm the country you are searching from is included in the app's availability. A staged rollout adds another layer: with a percentage-based production rollout, only that fraction of eligible users receives the update or, for a new app, the release, so some users will not see it yet.
Fix these by checking the app's country availability list and, for rollout, either increasing the rollout percentage or accounting for the fact that not all users are included yet. During a staged rollout, the direct URL still confirms the app is live, but search visibility for any given user depends on whether they fall within the rollout. Widening availability and completing the rollout removes these as causes.
Managed publishing and incomplete publishing
If the direct URL does not load, the app is not live, and Managed Publishing or incomplete publishing is often why. Per Google's Managed Publishing documentation, changes stay held until you publish them, so a release you approved may still be sitting unpublished. Similarly, a listing with unfinished required sections, an incomplete content rating, or a release still in review will not go live.
Resolve this by publishing any held changes in Managed Publishing and confirming every required section of the listing is complete and the release has passed review and rolled out. Once the release is genuinely live, the direct URL loads, and you move back to the discovery causes above. Keeping the two cases separate, not-live versus live-but-not-found, is what tells you whether to work on publishing or on indexing and compatibility.
Causes and fixes
Matching the cause to a fix depends first on whether the direct URL loads. The table below pairs the common causes with their fixes.
| Cause | What it looks like | Fix |
|---|---|---|
| Indexing delay | Live at URL, not in search yet | Wait a few hours and search again |
| Device incompatibility | Not shown on the searching device | Search from a device meeting all requirements |
| Country not covered | Not shown in a given country | Add the country to availability |
| Staged rollout | Only some users see the release | Increase the rollout percentage |
| Managed Publishing on | URL does not load, release held | Publish the held changes |
| Incomplete publishing | URL does not load, sections unfinished | Complete the listing and pass review |
Read the table starting from the direct URL test. A live URL points to the top rows; a failing URL points to the bottom rows.
Fix checklist
Working through the checks in order isolates the cause. The checklist below covers the steps.
| Check | Action | Done? |
|---|---|---|
| Direct URL | Confirm the app loads at its store URL | [ ] |
| Indexing | Waited a few hours after publishing | [ ] |
| Device | Searching from a compatible device | [ ] |
| Country | App available in the searching country | [ ] |
| Rollout | Rollout percentage high enough | [ ] |
| Publishing | Managed Publishing off or changes published | [ ] |
The first check settles half the question: if the URL loads, work the indexing and compatibility rows; if it does not, work the publishing rows. Do not skip the direct URL test.
Scan the published build
Once your app is live in the store, the build users download is the one that matters, which makes it worth confirming that build is secure. Resolving a visibility problem gets people to your listing; it does not tell you whether the shipped build carries risky third-party code, leaked keys, or over-broad permissions.
A scanner like PTKD.com analyzes your build and reports findings by severity, mapped to OWASP MASVS, so you know what the published app actually contains. To be clear about the boundary: PTKD does not change your store visibility, indexing, or device compatibility. It checks the build itself, which is a separate and worthwhile step once the app is live.
What to take away
- A published app that is not in the store is usually a discovery problem; confirm it is live by opening its direct store URL before assuming publishing failed.
- A newly published app becomes searchable a few hours after it is live, so wait and search again rather than treating an indexing delay as a failure.
- Device compatibility filtering hides the app from devices that do not meet its declared requirements, so test discovery from a fully compatible device.
- Country availability and staged rollout also hide a live app from specific users; widen availability and complete the rollout as needed.
- If the direct URL does not load, the release is not live, so publish held Managed Publishing changes and complete the listing, then scan the live build with PTKD.com.
