App Stuck in Waiting for Review? What It Means and What to Do

An app stuck in waiting for review is almost never a sign that something is wrong with your app. The status has one meaning: Apple has your submission and nobody has started on it. That is a queue, not a verdict. The expensive mistakes happen next, when a founder with a fixed launch date starts pulling levers that reset the queue.

This is the guide I give founders when an app stuck in waiting for review is threatening a date. It covers what the statuses mean, what Apple publishes about timing, what an expedite request can and cannot do, and how to set a launch date around a queue you do not control. What to prepare before you submit lives in the mobile MVP launch checklist. What reviewers reject lives in the piece on shipping a vibe-coded app.

In Review vs Waiting for Review: What Each Status Means

The difference between in review vs waiting for review is the difference between a line and a desk. Apple's App Store Connect help defines Waiting for Review as: you submitted a new app or updated version, Apple received it, and has not started the review. In Review means App Review is reviewing it right now.

So an app stuck in waiting for review has not been looked at by anyone. No reviewer has judged your screenshots, your paywall or your login. Nothing you did is being held against you, because nothing has been read yet.

While you wait, you can still edit some information and remove the build from review. You cannot upload or edit screenshots or app previews. That detail matters later, because it tells you what you can fix without leaving the queue.

What Apple Says About App Store Review Time

Apple publishes a goal, not a guarantee. The App Review page says it typically reviews at least 50% of submissions in less than 24 hours and 90% in less than 48 hours. Treat that as the app store review time you plan around on a normal week.

Read the sentence carefully. "At least 50%" and "90%" describe the population, not your submission. Roughly one build in ten is outside the 48-hour window even when everything is healthy. If you are that one, the numbers do not apply to you, and no setting in App Store Connect will show you why.

Apple has also told the trade press that its average review time across all apps is about a day and a half, and that updates to existing apps are prioritised. I could not confirm that from an Apple page, so take it as context. In October, developers on Apple's own forums reported waits of a week or more, and I cannot size how widespread that is. Plan for the published numbers and keep a buffer for the weeks when they are missed.

Why Your App Stuck in Waiting for Review Can Take Longer

Apple's review status page names what can keep an app stuck in waiting for review longer. The ones I see most often:

• An app with little review history, which describes every first submission.
• A submission that needs documentation, such as authorisations or licences.
• Complex or sensitive features: regulated content, new platform capabilities, enabled entitlements.

Minor updates and bug fixes usually move fastest, which is the other side of the same coin. A first version of a new app from a new developer account sits at the slow end of the range. That is not a penalty; it is how the queue is ordered.

In my experience the cause of a long wait is rarely in your control, and the cause of a slow In Review stage often is. A reviewer who cannot sign in to your app cannot finish. Put a working demo account in the review notes, and say plainly how to reach any feature behind a login or a payment. That removes the most common reason a review stalls after it starts.

What to Do While Your App Is Stuck in Waiting for Review

With an app stuck in waiting for review, most days the right action is nothing. If your submission is inside two days, you are inside Apple's own window. After that, work through this list in order:

1. Check the status, not the rumour. Forum threads about app review delays are a poor guide to your own build. Check App Store Connect, and set up status webhooks if you want a message when it changes.
2. Confirm the submission is complete. Review notes filled in, demo account working, contact details correct. Fix what you can without touching the build.
3. Do not resubmit to "bump" it. Apple's guidance is to resubmit only after a rejection you have fixed, and a new build starts a full review. Developers report that withdrawing and resubmitting restarted their wait. I cannot verify the mechanism, so I treat it as a risk with no upside.
4. Contact App Review if the delay is well past the stated range, through the contact form Apple provides for submission questions. Be specific: app name, version, date submitted, what you need.

Notice what is missing: new builds, new screenshots, a changed app name. Each of those is a reason to leave the queue. Founders do it because it feels like progress. It is the opposite. If the review finally ends in a spam rejection, guideline 4.3 design spam explains what to change before the next submission.

How to Request an Expedited App Review

Apple allows you to request an expedited app review, with limits. The request is for genuine urgency, such as fixing a critical bug or timing a release to an event you are directly associated with. Apple's note says requests should be reserved for matters of genuine urgency.

How it works, from Apple's help page:

• Only a submission that has already been sent to App Review can be expedited. Submit first, then ask.
• You file the request through Apple's expedite form, choosing the app and platform.
• App Review evaluates it and expedites "as allowed by availability and demand". That wording is not a promise.

What to put in the review notes depends on the reason. For a critical bug fix, include the steps to reproduce the bug in the current version. For an event, include the event, its date and how your app is connected to it. "We would like to launch on Friday" is a preference. Apple's examples set a higher bar.

Developers report that some requests are accepted and the app still sits in the queue, and that replies from support can be slow. So treat a request to expedite an app review as a lever that may help, not a plan. If your launch only works when the request is granted, the plan is the problem.

Plan the Launch Around a Queue You Do Not Control

The durable fix for any app stuck in waiting for review is to stop letting the review decide your launch date. Three habits do most of the work.

Submit earlier than feels necessary. Count back from the date that matters. I add at least a week for a first submission and a few days for an update, and I add more if anything on the list above applies. If you are spending a calendar line on this, the cost to publish an app is the place to see the rest of the bill.

Separate approval from release. Apple's Pending Developer Release status means the app was accepted and you still need to release it. Choose manual or scheduled release in App Store Connect. Then the review can finish whenever it likes, and the public launch happens when your marketing, support and servers are ready. This also settles the event case: schedule the release, as Apple recommends, instead of racing the queue.

Never promise an app store date to anyone outside the team. Press, partners and investors get a launch window, not a day. A founder who announced "live Tuesday" and then waited nine days has learned this once and will not forget it.

What I Would Do on Day One of the Wait

If a founder tells me they have an app stuck in waiting for review, I ask four questions before anything else. How long has it been in the queue? Is the demo account working today? Is there a date that cannot move, and what exactly is it tied to? Has anyone resubmitted or uploaded a second build?

If the answers are "under two days", "yes", "no hard date" and "no", I tell them to close the tab. If a real event is attached, we write the expedite request with the evidence Apple asks for, and we schedule the release so a late approval costs nothing. If the wait is long past the published range, we contact App Review with specifics and keep the build exactly where it is.

None of this needs a rescue. It needs someone who has been through the queue before and does not touch the build out of anxiety.

The Bottom Line

An app stuck in waiting for review is a place in line, and the way to keep your place is to leave the build alone. Know the two statuses, plan around the 24 and 48 hour goals rather than trusting them, request an expedited review only for a real reason, and release when you are ready instead of when you are approved. If you want a second pair of eyes on a submission before it goes in, see the engagement model on the services page, or tell me about your project.