You submitted your build, watched the status change to “Waiting for Review,” and then… nothing. A day passes. Then three. Then a week. If you’re refreshing App Store Connect wondering whether something’s actually wrong or you’re just being impatient, you’re not alone — this is one of the most common sources of anxiety for indie developers and small teams shipping their first (or fifteenth) app.
Table of Contents
- Quick Answer
- Understand What Your Status Actually Means
- How to Get Unstuck
- Tips / Common Mistakes
- App Store review delays FAQs
- Build It With GTStudios
This guide walks through what each App Store Connect status actually means, how long is normal versus how long means you should act, and the specific steps to take to get your app moving again — including when and how to request an expedited review or appeal a rejection.
Quick Answer
Most app updates clear review within a day or two, and new app submissions typically take a bit longer, sometimes a few days, especially if it’s your first app or you’re entering a new category. If your app has sat in “Waiting for Review” for more than about five to seven days with no change, it’s reasonable to contact Apple Developer Support. If it’s stuck “In Review” for more than 48 hours, that’s a better sign something specific is being checked (like in-app purchases or content) rather than a queue backlog.
Understand What Your Status Actually Means
App Store Connect shows a handful of statuses, and they don’t all mean the same kind of “stuck.” “Waiting for Review” means your build is in the queue and hasn’t been picked up by a reviewer yet — this is where most of the waiting happens, and it can sit unchanged for days without anything being wrong. “In Review” means a reviewer (or an automated + human combination) is actively testing your build; this stage usually resolves within hours to a day, so if it lingers much longer, it often means the reviewer hit a snag, needs to test an edge case, or is escalating something internally.
“Pending Developer Release” just means Apple approved it and is waiting on you to hit release if you chose manual release. “Rejected” or “Metadata Rejected” means a reviewer found an issue — metadata rejections (screenshots, description, keywords) don’t require a new build, while binary rejections do. “Invalid Binary” is a technical failure (missing entitlements, wrong architecture, etc.) that’s flagged automatically before a human ever looks at it.
Before you panic, check the Activity tab and Resolution Center in App Store Connect for any messages — sometimes Apple has already told you what’s wrong and it’s easy to miss the notification.
How to Get Unstuck
First, check Resolution Center for a message from the review team — a quick reply clarifying your app’s functionality or purpose can resolve a stall without a new submission. If there’s no message and you’ve genuinely been waiting past the normal window, contact Apple Developer Support directly through the Contact Us form on developer.apple.com, choosing the App Review topic, and reference your app name, Apple ID number, and submission date so the reply doesn’t require back-and-forth.
If your situation is genuinely time-sensitive — a critical bug fix, a security patch, or an update tied to a scheduled event or press moment — you can request an expedited review through the same Contact Us flow. Apple reserves expedited reviews for real urgency, not routine releases, so be specific about the impact and the deadline. Don’t submit a second, near-identical build while the first is still in review; that can reset your place in the queue or create confusion for the reviewer looking at two versions of the same app.
If your app comes back Rejected and you believe the decision was a mistake or a misunderstanding, reply in Resolution Center first with a clear, specific explanation tied to the exact guideline cited. If that doesn’t resolve it, you can escalate to the App Review Board for a formal re-evaluation — this takes longer than a standard review, so use it when you’re confident the rejection was in error, not as a first response to every rejection.
Tips / Common Mistakes
Don’t resubmit repeatedly hoping a new attempt will “reset” the queue faster — it doesn’t, and it can make your history look inconsistent to reviewers. Don’t ignore the Resolution Center; replies there generally get answered faster than starting a new support ticket from scratch. When you do write to Apple or reply to a rejection, keep it short, specific, and tied to guideline language rather than general frustration — reviewers respond faster to concrete evidence (a screen recording, a specific guideline number, a clear explanation of app functionality) than to a long narrative.
First-time submissions and apps entering sensitive categories (health, finance, kids, crypto) tend to take longer and get more scrutiny, so build in buffer time before a launch date or press embargo rather than assuming a same-day approval. And keep your test account credentials and demo instructions in App Review Information current — a huge share of avoidable rejections and delays come from reviewers simply not being able to log in or reproduce a feature.
Explore more: more app development guides.
App Store review delays FAQs
How long does App Store review normally take?
Most updates clear within a day or two. New app submissions and apps in more sensitive categories can take longer, sometimes several days, particularly for a developer’s first submission.
What’s the difference between ‘Waiting for Review’ and ‘In Review’?
‘Waiting for Review’ means your build is queued and hasn’t been picked up yet, which can sit unchanged for days. ‘In Review’ means a reviewer is actively testing it, and this stage typically moves within hours to a day.
When should I request an expedited review?
Only for genuinely urgent situations, such as a critical bug fix, a security issue, or an update tied to a fixed external deadline. Apple grants these selectively, so explain the specific impact and timeline when you ask.
Can I resubmit while my app is still in review?
It’s best not to. Submitting a near-identical build while the original is still being reviewed can confuse the review process or slow things down rather than speed them up.
What should I do if my app gets rejected?
Read the specific guideline cited, reply in Resolution Center with a clear and specific explanation or fix, and only escalate to the App Review Board if you believe the rejection was made in error after that initial reply.
Build It With GTStudios
Need help with your website, app, or small-business tech? GTStudios builds web, apps, and software for small businesses. See how GTStudios can help.
Want dev news in your inbox? Subscribe to the free newsletter.
Originally published at gtstu.com.
Top comments (0)