App Stuck 'In Review'? Every Status, What's Normal, and What to Do

If your app has been sitting in "Waiting for Review" or "In Review" for a day or two, it's almost certainly not stuck — it's just in the queue. Apple's own App Review page says the vast majority of submissions are reviewed within 24 hours (it has historically cited around 90% in under a day), but a real backlog of a few days happens all the time, especially around major holidays and the weeks after a new iOS launch. "In Review" can sit for anywhere from a few minutes to more than a day, and the status barely moves while it does. That silence feels like something broke. Usually nothing did.

It's worth worrying only when a submission sits far past that window (several days in "Waiting for Review," or over a day in "In Review" with no word), or when the status quietly changed to something waiting on *you* and you missed it. This guide walks every submission status, flags which ones are normal to sit in and which mean stop-and-act, and gives you the exact message to send Apple when it really has stalled.

App Store Connect shows a specific status for every submission, and the word choice tells you exactly whose move it is. Here are the ones you'll actually see, and what each one is really saying:

Use a rough rule of thumb, not a stopwatch. A day or two in Waiting for Review is normal; three-plus days with zero movement and no backlog you can point to (no holiday, no OS launch) starts to look stuck. In Review overnight is normal; well past a day with no result is on the edge. The real tell is a status that hasn't budged over a stretch clearly longer than your category's norm, with nothing sitting in Resolution Center waiting on you.

Before you contact anyone, rule out the boring causes: an unanswered message in Resolution Center, an unsigned agreement in Agreements, Tax, and Banking, or a build still showing Processing in the Builds section (a build that never finished processing can't be reviewed). Any of those holds a submission indefinitely and looks exactly like Apple being slow. Apple also publishes a Developer System Status page — if App Review itself is mid-incident, it shows there, and the answer is just to wait it out.

These two look similar in the dashboard and are very different in effort. Metadata Rejected means the build is fine — App Review just wants something changed in the listing: a screenshot showing the wrong thing, a description that overclaims, a support URL that 404s, an age rating that doesn't match. You fix it right in App Store Connect and reply in Resolution Center. You do not need to upload a new binary — that's the whole point of the status.

Rejected means the build itself tripped a guideline, so a metadata tweak won't clear it — upload a corrected version or argue the point in Resolution Center. The message names the guideline; read it literally. One of the most common and most misunderstood is the spam guideline (4.3), which rejects your *concept* rather than any line of code: no new binary clears it until you either differentiate the app or make the case in Resolution Center. Read the exact guideline number Apple cites and answer that specific one, not a generic 'please reconsider.'

Once you've confirmed it's genuinely past the normal window and nothing's waiting on you, work through these before you fire off a support message — they resolve most 'stuck' submissions without one.

When a submission has genuinely stalled, reach App Review through the Contact Us form in App Store Connect (or Apple's App Review contact page). Keep the message factual and complete so nobody has to write back asking for basics. A message that includes every identifier gets actioned faster than a panicked one that makes them go looking. Something like this works:

Apple lets you request an expedited review for critical situations — a serious bug affecting users of an app that's already live, or a time-sensitive event tied to a real date. You ask through Apple's expedite request form, and Apple grants it at its discretion. It's a genuine lifeline when you qualify, and it can move a review from days to hours.

Two honest caveats. Expedite is not a launch accelerator — 'I want to go live sooner' isn't a critical situation, and asking for it as one wastes the mechanism. And Apple watches how you use it: lean on expedited reviews for ordinary submissions and it may decline your future requests when you actually need them. Save it for the real emergency and it'll be there.

Clearing review gets you onto the shelf. It doesn't get you a rating — that begins the moment your first users show up. And here's the thing nobody tells you about the far side of App Review: the reviews come in on both stores, in every language your users speak, at hours you're asleep, and answering them is one of the few genuinely cheap levers on your rating. When Google announced recency-weighted ratings at I/O 2019, it reported that developers who respond to reviews see an average lift of 0.7 stars. Apple has never published an equivalent figure, but the mechanism is the same on both stores: an annoyed user reads a real, specific reply and quietly revises the score. We unpack how that works in [does replying to app reviews raise your rating](/blog/does-replying-to-app-reviews-raise-your-rating), and the tone that actually turns a 2-star around in [how to respond to negative app reviews](/blog/how-to-respond-to-negative-app-reviews).

A short worked example — the kind of review a freshly-launched app catches in its first week, and the reply that turns the star around:

That reply is specific, names the fix, and gives the reviewer a reason to change their star. Do it once and it's a nice afternoon. Do it for every review across the App Store and Google Play, in each reviewer's own language, without letting the queue lapse during a launch week — that's the part that quietly eats a founder's time right when they have the least of it. ReplyArgus can't speed up App Review; nothing can except Apple. What it does is wait for you on the other side.

So 'stuck in review' is usually the queue doing its job, not a failure — the real skill is telling a normal wait from a genuine stall, and knowing that most stalls are a status quietly waiting on you. Rule out the boring causes, respect the backlog, and reach Apple with a specific message only when it's clearly past normal. Then get through it, because the shelf is the easy part. [Start free with ReplyArgus](/signup) — no card — and the day after you're approved, Argus drafts your first reply in minutes, in the reviewer's own language.