App Store review time in 2026: real waits and a launch plan

Originally published on AppRanker.

App Store review time is the one part of an iOS release you can't schedule, and it's usually the reason a launch date slips. Below is what the numbers actually look like, what each App Store Connect status is telling you, and a timeline that keeps your release date safe even when the queue is slow.

The three numbers worth knowing

Ask "how long does review take?" and you'll get three different answers depending on who you ask. All three are useful, as long as you know what kind of number each one is.

Source	Figure	How much to trust it
Apple's App Review page	At least 50% of submissions reviewed in under 24 hours, 90% in under 48 hours	Official target, not a promise
Runway's public review-time tracker	About 7h 13m waiting plus 2h 4m in review, averaged over a two-week window ending October 6	Real data, but only from teams that use Runway
Apple Developer Forums	New apps stuck in Waiting for Review for 10 to 15+ days	Anecdotes; people with fast reviews don't post

What this adds up to: updates to established apps usually clear within a day or two, while long waits cluster around new apps. Also notice that most of the time goes to waiting in the queue, not to the review itself. Apple doesn't say whether first submissions are queued differently, but a new app gives the reviewer much more surface to inspect, from the core idea and pricing model to account setup and each screen.

Read the status before you panic

Most "is my app stuck?" questions are answered by the status label. Here's what each one means for you:

Status	Whose move it is
Ready for Review	Yours: metadata is done, you haven't submitted
Waiting for Review	Apple's: received, review not started
In Review	Apple's: a reviewer has it, so keep an eye on your inbox
Pending Developer Release	Yours: approved, waiting for you to press release
Processing for Distribution	Nobody's: should be ready within 24 hours
Ready for Distribution	Done: check the listing in each storefront
Rejected	Yours: fix what the rejection names, then reply or send a new build
Metadata Rejected	Yours: correct the listing text and reply; the binary is fine
Developer Rejected	Yours: you pulled it, resubmit when ready

Two you'll see less often: Pending Apple Release means Apple is holding a build until the OS version it targets ships publicly, and Waiting for Export Compliance puts your encryption paperwork through its own queue, independent of App Review.

Why some submissions crawl

Apple doesn't publish how its queue works, but it does say plainly that incomplete submissions get delayed or rejected. That's the one factor you fully control. Before you hit submit, check for these common gaps:

• A demo account that is missing, has expired, or needs two-factor auth the reviewer can't get past
• Features that need special hardware, a location or a paid tier, with nothing in the review notes explaining how to reach them
• An API that is offline or still wired to a staging server
• In-app purchases left out of the submission with the build

Queues also tend to stretch when everyone ships at the same moment, for example right after a new OS or device launch. Extra items like In-App Events, custom product pages and creative assets can go to review too. Apple's Asset Library lets you get creative assets approved ahead of time, so they don't have to ship with a build at the last minute.

Separate approval from release

This habit gets rid of most review-time stress. In the version's release options, choose either Manually release this version or automatically release no earlier than a date you pick. You submit early, the approved build waits for you, and you release on launch day. After release, allow up to 24 hours for it to show up on the App Store. Apple sends a reminder if a version stays in Pending Developer Release for more than 30 days.

For updates, phased release spreads the rollout across 7 days, stepping from 1% to 2%, 5%, 10%, 20%, 50% and finally 100% of auto-updating users. You can pause it for up to 30 days in total or push it to everyone at any point. It doesn't make review faster, but it limits the damage from a bad build, which means fewer emergency resubmits.

A launch timeline that leaves room for a slow review:

1. 3 to 4 weeks out: send the first build to an external TestFlight group. Only the first build needs a beta review, so any review questions come up early.
2. 2 weeks out: finish the listing, screenshots, privacy details and in-app purchases.
3. 7 to 10 days out: submit for review with manual release selected.
4. After approval: check the listing and get your links and launch posts ready.
5. Launch day: release, and expect up to 24 hours before it appears everywhere.

When it's really stuck

Go through these before writing to Apple:

1. Look for anything flagged in App Store Connect: Resolution Center messages, export compliance questions, unsigned agreements, tax or banking forms, an unpublished App Privacy section.
2. Make sure the demo account still works and the back end is live.
3. Don't cancel and resubmit to "bump" the app. Apple's docs don't say it helps, and you end up in Developer Rejected until you submit again.
4. Contact App Review through the signed-in contact form, with your submission date and app ID.

Expedited review is meant for real emergencies, like a critical bug or a release tied to an outside event, and you can only request it once the build has been submitted. A launch date you picked yourself doesn't count. Put the justification in the Notes field, and include repro steps if it's a bug:

Critical bug fix: v3.4.1
v3.4.0 crashes on relaunch for users who signed in with Apple.
Repro on 3.4.0:
1. Install on a device running the affected iOS version
2. Use Sign in with Apple
3. Kill the app, launch again -> crash on splash screen
3.4.1 only touches session-restore code.
Demo account details are in App Review Information.

There's no paid fast lane. Apple says App Review works around the clock, but it doesn't publish separate figures for weekends or holidays.

Key takeaways

• Apple's target is 50% of submissions reviewed in under 24h and 90% in under 48h. It's a goal, not a guarantee.
• Most of the wait is queue time, and multi-week waits are mostly reported for new apps.
• A complete submission (working demo account, live back end, IAPs attached, clear notes) is the lever you control.
• Submit 7 to 10 days early with manual release, and send a TestFlight build 3 to 4 weeks out.
• Never cancel and resubmit to jump the queue. Save expedite requests for real emergencies.

The original post covers every status, the FAQ and the sources in more depth: how long App Store review takes in 2026 and what to do when you're stuck. Once your app is approved, you can also list it on the AppRanker app leaderboard for iOS and Android apps.

What's the longest you've waited in Waiting for Review, and was it a new app or an update?