If Play Console shows your update as Published but it is not showing in the store yet, that gap is normal: Published means the update is live on Google's side, but it still takes time to propagate across Google's servers and to reach each device's Play Store cache before users see it. This usually takes a few hours, and full availability everywhere can take up to about a day, so it is not instant. Two other things commonly explain a missing update: if you used a staged rollout below 100 percent or paused it, only a portion of users receive it, and each user's Play Store app caches the listing, so an update may not appear on a specific device until that client refreshes. If your rollout is at 100 percent and it has been more than a day, that is when to look closer.
Short answer
Published in Play Console means the update is live, but propagation and caching delay when users actually see it. Per Google's publishing guidance, a published update takes time to propagate across Google's systems, typically a few hours and up to about a day for full availability, rather than appearing instantly. Per Google's staged rollout documentation, a rollout below 100 percent or a paused rollout means only some users get the update. The Play Store app also caches listings, so a device may show the old version until it refreshes. If your rollout is full and it has been over a day, check the release status before escalating.
Published in Console versus available to users
The core confusion is that Published in Play Console does not mean instantly visible to every user, because there is a real gap between the release going live on Google's side and it reaching users' devices. When Play Console marks your release as Published, your update has been accepted and is live in Google's systems, but the store is a globally distributed service, so the update has to propagate across Google's servers and then be picked up by each device's Play Store app before a user sees the new version. Published is the start of that distribution, not the end.
This is why you can see Published in the Console while your own phone still shows the old version. The status reflects Google's side, not the cache on any particular device or region at a given moment. So the right way to read Published is that the update is on its way to users, and when a specific user sees it depends on propagation and their device cache, not on the Console status alone, which has already done its part.
How long propagation takes
Propagation of a published update typically takes a few hours, and full availability across all regions and devices can take up to about a day. Many users see the update well within a few hours, but because the store is distributed and updates roll out gradually, there is no exact moment when it appears everywhere at once, so you should expect a window rather than an instant switch. A wait of a few hours after Published is entirely normal and not a sign of a problem.
There is no guaranteed propagation time, so judge the wait against this rough window rather than a fixed deadline. Within a few hours to a day, a not-yet-visible update is normal, given device caches and staged rollout. It becomes worth investigating when the rollout is at 100 percent, a full day or more has passed, and users still are not receiving it, at which point the cause is more likely a rollout setting, a stale device cache, or a support case than propagation still in progress.
Is store caching regional?
Google Play's propagation is global and gradual, so there is variation in when an update surfaces, and both server-side propagation and device-side caching contribute to it. As the update rolls out across Google's distributed infrastructure, it becomes available to different users and regions over a span rather than all at once, so it is normal for the update to appear for some users before others. This is not a fixed regional schedule you can look up, but a gradual availability that means timing differs across users and locations.
On top of the server side, the Play Store app on each device caches listing data, so even once the update is available to a device's region, that device may show the old version until its Play Store client refreshes its cache. So the perceived delay is a combination of the update propagating across Google's servers and the individual device not yet having refreshed. Both resolve with time, but they explain why the update can look absent in one place or on one phone while it is already live elsewhere, which is expected behavior rather than a fault.
Does a rollout pause affect store display?
Yes, a staged rollout that is paused or set below 100 percent directly affects who sees the update, because only the included portion of users receives it. If you released the update as a staged rollout at a percentage, users outside that percentage continue to see the previous version, so the update legitimately does not show for most users by design. And if you paused the rollout, you stopped it from reaching further users, so the update stalls at whatever share it had reached.
So before assuming a propagation problem, check your rollout settings in Play Console. If the release is a staged rollout below 100 percent, that is why many users do not have the update, and increasing the percentage, or completing the rollout to 100 percent, is what extends it to everyone. If the rollout is paused, resuming it lets it continue. A rollout setting is a common and easily overlooked reason an update is not showing broadly, and it is entirely within your control, unlike propagation timing.
Device-level refresh
On an individual device, an update may not appear until the Play Store app refreshes, so a device-level refresh can surface it sooner. Because the Play Store caches listings, your own phone, or a user's, might keep showing the old version even after the update is available to that region. Reopening the Play Store, pulling to refresh the app's page, or, more forcefully, force-stopping the Play Store app or clearing its cache in system settings, prompts the client to fetch current data, which often reveals the update if it is available to that device.
This matters when you are checking your own update and it seems absent, because your device's cache may simply be stale. A device-level refresh confirms whether the update has reached that device rather than whether it exists at all. Keep in mind that if the update genuinely has not propagated to the device's region yet, or the device is outside a staged rollout, a refresh will not conjure it, so use the refresh to rule out a stale cache, and account for propagation and rollout for the rest.
Does resubmitting reset review?
Yes, uploading a new release to try to force the update out starts a fresh review, so resubmitting because the update is not showing usually backfires. A new release enters review as a new submission rather than speeding up the propagation of the one you already published, so canceling and re-releasing can send you back into review and delay things further. The published update is already live; it just needs to propagate.
So the rule is to wait for propagation rather than resubmit while a published update is still rolling out, and to check your rollout percentage and refresh your device instead of uploading again. Only submit a new release when you actually have a change to make, not as a way to nudge distribution. Resubmitting a materially identical release trades an update already published and propagating for a new one that must be reviewed again, which is slower than letting the current one reach users.
Propagation timing at a glance
Matching how long it has been to the likely cause tells you whether to wait or act. The table below maps it.
| Time since Published | Normal? | Likely cause |
|---|---|---|
| Minutes to a few hours | Normal | Propagation and device caching |
| Up to about a day | Normal for full availability | Gradual global rollout |
| Some users have it, others do not | Normal | Staged rollout or caching |
| Over a day at 100 percent rollout | Worth investigating | Rollout setting, cache, or a support case |
Read the table together with your rollout setting, since a staged rollout below 100 percent explains a missing update regardless of how much time has passed.
What to check
Working through these checks explains a missing update. The checklist below covers them.
| Step | Action | Done? |
|---|---|---|
| Confirm Published | The release shows live in Play Console | [ ] |
| Check the rollout percentage | Full 100 percent, or a staged or paused rollout | [ ] |
| Allow propagation | Wait a few hours to about a day | [ ] |
| Refresh the device | Reopen or clear the Play Store cache | [ ] |
| Do not resubmit | Wait rather than restart review | [ ] |
| Escalate if it persists | Contact support past the normal window | [ ] |
The check that most often explains a broadly-missing update is the rollout percentage, since a staged rollout below 100 percent limits who receives it by design.
Use the wait to secure the update
While your published update propagates to users, that time is well spent confirming the update you shipped is sound, rather than only refreshing the store, since it is now reaching real devices.
A scanner like PTKD.com analyzes your build and reports issues such as over-broad permissions, risky third-party code, and leaked keys by severity, mapped to OWASP MASVS, so you can verify the update as it rolls out. To be clear about the boundary: PTKD does not publish your app, control the rollout, or speed up propagation. It helps you use the propagation window to make sure the update reaching users is one you have verified.
What to take away
- Published in Play Console means the update is live on Google's side, but it takes time to propagate to users' devices, typically a few hours and up to about a day for full availability.
- Store availability rolls out gradually across regions and devices, and the Play Store app caches listings, so an update can appear for some users and devices before others.
- A staged rollout below 100 percent or a paused rollout means only a portion of users receive the update, which is a common and controllable reason it is not showing broadly.
- On a device, reopening or clearing the Play Store cache can surface an available update, but it will not conjure one that has not propagated or is outside a staged rollout.
- Do not resubmit to force it, since that restarts review, and use the propagation window to verify the update with a tool like PTKD.com.
