An app stuck in review on Google Play Console is usually normal, not broken. Google says review can take from a few hours up to seven days, and longer in exceptional cases, so a wait of several days is within range. New developer accounts face extended reviews, and new personal accounts must run closed testing for fourteen days before they can even apply for production, which is where the "two weeks" often comes from. Unpublishing or resubmitting does not speed it up. If your status reads "Pending publication," the release is already approved and waiting for you to publish it.
Short answer
Most apps stuck in review are simply in Google's normal queue, which the Play Console Help says can run from a few hours up to seven days, or longer in exceptional cases. New accounts and policy-sensitive apps get extended reviews, so several days is not abnormal. Resubmitting a new release restarts the clock rather than speeding it up, and unpublishing the app does not help. If the status is "Pending publication," the update is approved and held by Managed Publishing until you publish it. Escalate to support only after you clearly pass seven days with no movement.
How long does Google Play production review take?
Google Play production review takes anywhere from a few hours to seven days, and occasionally longer, and Google does not promise a fixed time. For established accounts with a straightforward app, an update often clears in a day or two. For a first release, a new account, or an app that touches sensitive areas, it routinely runs closer to the upper end or beyond.
The honest takeaway is that there is no service-level guarantee and no live progress bar. Google publishes a range, not a deadline, which is exactly why a review that has run four or five days can still be completely normal. Plan a buffer of at least a week between submitting and your intended launch date.
Why does it take 2 weeks (or more)?
Two weeks usually reflects one of two things: an extended review, or the testing requirement for new personal developer accounts. Accounts created recently are subject to longer reviews by default, so the same app that a mature account ships in a day can take a new account far longer.
The bigger factor for new personal accounts is the closed-testing requirement. Google requires these accounts to run closed testing with at least twelve testers for at least fourteen days before they can apply for production access, per the Play Console Help. That fourteen-day window is not a review delay at all; it is a gate you must pass before production, and it is the most common reason a new developer feels their launch is stuck for two weeks.
Is it review, or is Managed Publishing holding the release?
Before assuming a delay, check whether your release is actually approved and simply held. With Managed Publishing turned on, Google reviews your update but does not publish it automatically; it waits until you press publish, as the Play Console Help explains. An approved release in this state shows as ready to publish, not live, which many developers misread as stuck.
Open the Publishing overview in Play Console and look for changes that are reviewed and waiting. If you see them, the fix is not to wait or contact support; it is to publish the changes yourself. Turning Managed Publishing off returns you to automatic publishing once a review completes.
Why is my app pending for days?
Several things extend a review beyond the quick path, and knowing which applies tells you whether to wait or act. A first release on a brand-new account, an app that requests sensitive permissions such as location, SMS, or accessibility, and periodic deeper policy checks all lengthen the queue. Public holidays and general backlogs add time that has nothing to do with your app.
The table below maps what you see to the likely cause.
| What you see | Likely cause | What it means |
|---|---|---|
| "In review" under 7 days | Normal queue | Wait, it is within range |
| "In review" on a new account | Extended review for new developers | Longer is expected |
| "Pending publication" | Approved, Managed Publishing is on | You need to publish it |
| "In review" past 7 days | Deeper review or a backlog | Consider contacting support |
| Update rejected or policy flag | A policy or permission issue | Fix it and submit again |
Most of these resolve on their own with time. The ones that do not, such as a policy flag, will show up as a rejection or a Policy Center notice, which is your signal to fix something rather than keep waiting.
Should you unpublish or resubmit to restart review?
No. Unpublishing your app does not restart or speed up a review, and it can cause more disruption than it solves, especially for an app that is already live. A review in progress will finish on Google's schedule whether or not you touch the listing.
Resubmitting is different but rarely helpful: creating a new release replaces the one in review and starts the process over, which usually costs you time rather than saving it. The only good reason to submit a new release is to fix a real problem, such as a policy issue Google flagged. Otherwise, leave the release in place and wait.
Step by step: what to do while stuck
Work from the calm, likely-normal explanations toward escalation, rather than reacting immediately. The checklist below gives a clear order for each situation.
| Situation | What to do first | Escalate? |
|---|---|---|
| Under 7 days in review | Wait, it is normal | No |
| New developer account | Expect longer, keep waiting | Not yet |
| Status is "Pending publication" | Publish it via Managed Publishing | No, it is approved |
| Past 7 days with no change | Check Policy status, then contact support | Yes |
| Explicit policy rejection | Fix the issue and submit a new release | No, resubmit |
Before you do anything drastic, confirm three things: that you are genuinely past seven days, that the status is not actually "Pending publication," and that there is no Policy Center notice waiting for your action. Those three checks explain the large majority of reviews that feel stuck, and each one takes only a moment to verify inside the console before you spend time on anything else.
When and how to escalate to support
Escalate when you have clearly passed seven days with no change and none of the normal explanations apply. Use the Play Console Help "Contact us" flow to open a case, and include your app's package name, the track, the date and time you submitted, and a screenshot of the status. Concrete details keep your case from bouncing back for more information.
Set realistic expectations. Google Play does not publish a support response time, and during backlogs replies can be slow. Escalation is the right move after a week, but it does not guarantee an instant release, particularly when the cause is a general review backlog rather than a problem with your app.
Scan the build before you submit
Some review delays turn into rejections, and a meaningful share of Play rejections trace back to security and privacy problems: an app requesting permissions it cannot justify, cleartext traffic where the policy expects encryption, data leaking through exported components, or an embedded secret that a reviewer's tooling flags. Each rejection sends you back to the queue you were trying to escape.
A scanner like PTKD.com analyzes your .apk and returns findings ordered by severity and mapped to OWASP MASVS, so you can fix permission, network, and storage issues before you submit rather than after a rejection. To be clear about its limits: a scanner does not speed up Google's review and it does not judge every policy rule, such as content or metadata requirements. What it does is remove the predictable security findings that turn a single review into two.
What to take away
- An app stuck in review is usually normal; Google Play review runs from a few hours to seven days, sometimes longer.
- The "two weeks" is often the new-account closed-testing requirement, at least twelve testers for fourteen days, not a review delay.
- Check whether the status is "Pending publication," which means the release is approved and Managed Publishing is holding it for you to publish.
- Do not unpublish, and only resubmit to fix a real policy issue, because a new release restarts the clock.
- Scan each build with PTKD.com to clear security and permission findings that would turn a review into a rejection.
