On Google Play, "In review" and "Pending publication" are two different stages, and confusing them leads to the wrong fix. In review means Google is still evaluating your update and it is not approved yet. Pending publication means the update has been processed or approved and is now in the publishing step, waiting to go live, often because of managed publishing or a staged rollout. If you are In review, the answer is usually to wait; if you are Pending publication for a long time, the hold is often something you control.
Short answer
In review means Google is reviewing your update, which usually takes hours to a few days, with an official ceiling of up to 7 days or longer in exceptional cases per the Google Play Help. Pending publication means the update is approved or processed and sits in the publishing queue, usually minutes to hours, unless managed publishing or a staged rollout is holding it. Resubmitting restarts review. If In review passes 7 days, contact support; if Pending publication is stuck, check managed publishing and your rollout settings.
In review vs pending publication: the difference
The difference is where your update is in the pipeline: In review is before approval, and Pending publication is after. In review means a combination of automated and, when needed, manual checks is still deciding whether your update is acceptable. Pending publication means those checks are done and the update is now being published, which is a separate step that you partly control.
This matters because the two statuses call for opposite actions. If you are In review, the ball is in Google's court, and the right move is almost always to wait. If you are Pending publication and it is not going live, the cause is usually on your side: managed publishing is holding the approved update for a manual release, or a staged rollout is releasing it to a small percentage first. Reading which status you are actually in tells you whether to wait or to click publish.
What "In review" means and how long it takes
In review means Google is actively evaluating your update, and it usually takes hours to a few days. Updates go through standard publishing, where Google processes changes as soon as possible, but each one passes automated checks and sometimes a manual review that adds time. The table below maps the statuses you will see to what is normal and when to worry.
| Status | What it means | Typical time | Alarm signal |
|---|---|---|---|
| In review | Google is reviewing the update | Hours to 3 days | Over 7 days with no change |
| Pending publication | Approved, being published or held | Minutes to hours | Over a day, or managed publishing is on |
| Published (Live) | Available on the store | Final state | (none) |
| Rejected or policy issue | A problem was found | Needs your action | Read the Policy Center |
Google gives no guaranteed time, so any figure is an average, not a promise. New or flagged accounts are reviewed more carefully, which adds time, and during a general backlog even a simple update can sit longer. If In review passes the 7-day mark with no change, that is beyond the normal range and worth escalating.
What "Pending publication" actually means
Pending publication means your update cleared review and is in the publishing step, not still under review. In most cases it goes live within minutes to a few hours. When it does not, there is usually a concrete reason you can find and fix, rather than a hidden problem on Google's side.
The two most common holds are managed publishing and staged rollout. With managed publishing enabled, Google reviews the update normally but does not publish it automatically; it waits for you to release it manually. With a staged rollout, the approved update is released to a small percentage of users first and reaches everyone only after you increase the rollout. Neither is a bug, and both explain a build that is approved but not fully live.
Why is it stuck in one and not the other?
The reason depends on which status you are in, which is exactly why the distinction matters. Stuck In review usually means the queue is busy, it is a first submission, the account is new or flagged, or a metadata or policy issue is holding the review. Stuck Pending publication almost always means managed publishing is waiting for your manual release, or a staged rollout has not yet reached everyone.
A separate case traps new personal accounts. Before you can publish to production at all, Google requires a closed test with at least 12 testers opted in for 14 continuous days, per the Google Play requirements. If your account is new and nothing seems to publish, the block may be this requirement rather than a slow review or a publishing hold.
Should you wait or resubmit?
If you are In review within the normal range, wait; resubmitting rarely helps and usually hurts. Uploading a new build of the same version replaces the one in review and restarts the process, sending you to the back of the queue. Resubmit only when you have genuinely fixed something that would have caused a rejection or a policy issue.
If you are Pending publication, do not resubmit at all, because there is nothing left to review. Instead, check whether managed publishing is holding the update and publish it, or check your staged rollout percentage. The calmest approach in both cases is to leave the update in place and take the one action that matches your actual status.
How to unblock each status
Match your action to the current status instead of guessing. The table below maps each state to the right next step.
| Current status | What to do | When to escalate |
|---|---|---|
| In review, under 3 days | Wait, this is normal | Not yet |
| In review, over 7 days | Check the Policy Center, then contact support | Immediately |
| Pending publication, not live | Check managed publishing and staged rollout, then release | Not usually needed |
| New account, nothing publishes | Complete the 14-day closed test requirement | Not needed |
| Rejected or policy issue | Read the Policy Center and fix | Only if it is a Google error |
Work the steps in order and note what you find. Many holds that look like a stuck review are really managed publishing waiting for your click, a staged rollout in progress, or an unread notice in the Policy Center. Ruling these out first avoids escalating over something you can resolve in a minute.
When to contact support
Contact support when In review clearly passes 7 days with no change, and after ruling out a publishing hold if you are Pending publication. Open a case from the Google Play Console Help and include the package name, the version number, the submission date and time, and screenshots of the status and any Policy Center notice. A complete case moves faster than one missing details.
Keep expectations realistic. Support can confirm status and pass your case along, but it does not speed up a review that is still in progress, and it cannot release an update that managed publishing is holding, because that action is yours. Escalate for a genuinely stuck review, and handle a publishing hold yourself.
Where a pre-submission scan fits
A rejection or policy issue sends a build back to the start of review, so avoiding an avoidable rejection is the fastest way to reach Published. An embedded secret key, a permission with no justification, or an insecure network setting can each cost you a full review cycle, which hurts most when review is already slow.
A scanner like PTKD.com analyzes your built .aab or .apk before you upload and returns a graded report mapped to OWASP MASVS, so you can fix what would trigger a rejection before it enters review. It is worth being clear about the limit: a scanner cannot speed up Google's review, release a held update, or resolve a policy notice. What it does is prevent the avoidable rejections that restart the wait, which matters most when your update is already stuck.
What to take away
- In review is before approval and means Google is still evaluating; Pending publication is after approval and means it is being published.
- In review usually takes hours to a few days; over 7 days is beyond normal and worth escalating.
- Pending publication that will not go live is usually managed publishing or a staged rollout, both of which you control.
- Resubmitting restarts review; leave the build in place unless you fixed a real rejection.
- Before you upload, scan the build with PTKD.com so an avoidable rejection does not restart the wait.
