If your Google Play update is stuck in review, the honest answer is that there is no button to expedite a standard review, so the real question is whether it is genuinely still in review or actually finished and waiting on you. Check Managed Publishing first: if it is on, a reviewed update sits held until you publish it, which is the most common reason an update looks stuck. Do not unpublish your app or cancel and resubmit to hurry it, because neither speeds up review and both can set you back. Within Google's up-to-7-days window, waiting is the right move.
Short answer
You cannot manually expedite a normal Google Play update review, so focus on whether the update is truly in review or just held. Per Google's Managed Publishing documentation, a reviewed update stays held until you publish it when Managed Publishing is on, so check that first, since it often explains a stuck update. Per Google's review guidance, reviews can take up to 7 days and occasionally longer, so within that window waiting is normal. Do not unpublish the app or cancel and resubmit to speed things up: neither expedites review, and both can make your situation worse. Contact support only after you clearly exceed the normal window.
Can you expedite a stuck update?
No, there is no mechanism to expedite a standard Google Play update review. Unlike some platforms that offer an expedited-review request, Google Play does not provide a button or form to move a normal update to the front of the queue, so no action on your side directly speeds up the automated and, where needed, human review. Accepting that up front saves you from trying levers that do not work and can backfire.
That does not mean you are helpless; it means the productive steps are different from expediting. You can confirm the update is actually in review rather than held, make sure nothing on your side is blocking publication, and wait out the normal window, then escalate a genuine overrun. What you cannot do is force the review itself to go faster. The rest of this comes down to distinguishing a real in-progress review from an update that is finished and waiting on a setting, and avoiding actions that reset your progress.
Is it actually Managed Publishing?
The most common reason an update looks stuck is that it has already been reviewed and is being held by Managed Publishing, waiting for you to publish it. When Managed Publishing is turned on, approved changes, including a reviewed update, do not go live automatically; they sit in a held state until you choose to publish them. So an update that seems stuck in review may in fact be done, with the only remaining step being your click to publish.
Check this before anything else. In Play Console, look at your Managed Publishing status and your publishing overview to see whether there are reviewed changes ready to publish. If there are, publishing them releases your update, and the apparent stuck state resolves immediately with no waiting involved. If Managed Publishing is off, updates publish automatically once reviewed, so this is not your cause, and you move on to judging the wait against the normal window. Ruling Managed Publishing in or out is the single highest-value check.
Does unpublishing help?
No, unpublishing your app does not help, and it can hurt. Unpublishing removes your live app from the Play Store for new users; it does nothing to the review queue for your pending update, so the review does not go faster while your existing listing disappears. Developers sometimes try this in the hope of resetting something, but the review and your live listing are separate, and unpublishing only damages the latter.
So treat unpublishing as off the table when your goal is to unstick a review. If your live app is fine, leave it published; taking it down loses you visibility and installs for no benefit to the pending update. The only outcome of unpublishing to hurry a review is that you now have two problems, a still-pending update and a removed listing, instead of one. Leave the published app alone and address the review through the checks that actually apply.
Does canceling and resubmitting help?
No, canceling and resubmitting does not help, because a resubmission starts a new review rather than advancing the current one. When you cancel a release and upload again, the new version enters review as a fresh submission, so an update that was already progressing does not move faster; it may simply begin the clock again. Repeatedly resubmitting to prod the queue is one of the most common ways developers extend their own wait.
The rule is to resubmit only when you have an actual change to make, such as fixing an issue the review raised, not as a way to hurry a review that is progressing normally. If your update is within the normal window and nothing is wrong with it, canceling and resubmitting trades a review that is on track for a brand-new one at the back of the line. Patience beats resubmission here, and it avoids resetting the progress you have already made.
Normal versus abnormal waiting
Judging your wait against the normal range tells you whether to keep waiting. Google states reviews can take up to 7 days and occasionally longer in exceptional cases, so anything within that window is normal, even though many updates finish much faster, often within hours to a couple of days. The up-to-7-days figure is the benchmark for what counts as normal rather than a delay you should act on.
Waiting becomes abnormal when you clearly pass that window with no decision and no request for information, and you have confirmed the update is genuinely in review rather than held by Managed Publishing. Before concluding something is wrong, rule out the held-update case and account for the fact that some reviews legitimately take several days. If you are within the window, wait; if you have exceeded it and the update is truly in review, that is the point where contacting support is reasonable rather than premature.
When and how to contact support
Contact support only after you have exceeded the normal window and ruled out Managed Publishing as the cause. Once you are clearly past the up-to-7-days benchmark with a genuinely in-review update and no decision, reach Google Play developer support through the Help option in Play Console, describe the situation, and include your package name and the submission timeline. Support can look into a review that has actually stalled, which is different from one that is merely slower than you hoped.
Make the request factual and singular rather than repeated. A clear message with your app details and dates is more effective than several messages, and sending many can slow rather than speed a response. Confirm before you write that the update is in review and not held, that you have not just submitted and expected an instant result, and that you are past the normal window. Meeting those conditions makes support the right next step rather than a premature one.
What helps versus what does not
Separating the actions that help from the ones that do not keeps you from making things worse. The table below compares them.
| Action | Does it help? | Why |
|---|---|---|
| Wait within the normal window | Yes | Automated review finishes on its own |
| Check and publish Managed Publishing | Often | A reviewed update may just be held |
| Unpublish the app | No | Removes your live listing, no effect on review |
| Cancel and resubmit | No | Restarts the review and sets you back |
| Contact support after the window | Yes | Support can look into a genuine overrun |
Read the table before acting: the yes rows are the productive moves, and the no rows are the tempting actions that either do nothing or hurt.
Decision guide
Matching your situation to the right move prevents wasted, counterproductive steps. The table below maps common cases.
| Your situation | Best move | Why |
|---|---|---|
| Managed Publishing is on | Publish the held update | It may be reviewed and waiting on you |
| Within the up-to-7-days window | Wait | The review is still in the normal range |
| Past the window, update truly in review | Contact support | It may be a real overrun |
| Tempted to unpublish or resubmit | Do neither | Both can hurt and neither expedites |
Read your case against the guide. The first row resolves many apparent stalls instantly, while the last row warns you off the actions that feel productive but are not.
Use the wait to verify your build
Since you cannot speed the review, the wait is time better spent verifying the build than refreshing the status page. A review that is merely slow can still end in a rejection if the build has a security or policy issue, so confirming the update is sound is a more useful use of the wait than trying to hurry it.
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 catch a problem during the wait rather than after a rejection. To be clear about the boundary: PTKD does not review your app for Google, expedite the queue, or change your review time. It helps you use the wait to make sure the update you submitted will hold up.
What to take away
- There is no way to expedite a standard Google Play update review, so focus on whether the update is truly in review or already reviewed and held.
- Check Managed Publishing first, since a reviewed update held for you to publish is the most common reason an update looks stuck.
- Unpublishing does not speed up review and removes your live listing, and canceling and resubmitting restarts the review, so avoid both.
- Reviews can take up to 7 days and occasionally longer, so wait within that window and contact support only after a genuine overrun with an in-review update.
- Use the wait to verify your build with a tool like PTKD.com so a slow review does not turn into a rejection.
