You submitted a build three days ago and App Store Connect still shows Waiting for Review — no move to In Review, no Resolution Center message, no email. Apple’s public commitment is that 90% of submissions get an approval-or-rejection decision within 24 hours (a commitment it formalized to the UK CMA effective April 1, 2026). So why is yours past that?
Fastest answer: As of June 2026 the queue is genuinely backed up — worldwide releases were up roughly 80% year-over-year on iOS in early 2026, and real-world waits now commonly run 24-72 hours, with first-version and sensitive-category submissions stretching to 5-7+ days. Before you touch anything, do two checks: (1) confirm every submission field shows a green status, and (2) open Resolution Center and look for an unanswered reviewer message. A silent block on your side is the one cause you can actually fix. Everything else is a waiting-vs-escalating decision, and the worst move is uploading a new build, which throws you to the back of the queue.
First, read the status correctly
App Store Connect statuses are easy to misread. Here is what each one means as of June 2026:
| Status | Who it’s waiting on | What it means |
|---|---|---|
| Waiting for Review | Apple | Received, not yet picked up by a reviewer. You can still edit some metadata. |
| In Review | Apple | A reviewer is actively looking at it. |
| Pending Developer Release | You | Approved — you must click Release to ship. |
| Ready for Distribution | Nobody | Approved and live (formerly “Ready for Sale”). |
| Unresolved Issues / Rejected | You | App Review flagged something; reply in Resolution Center. |
| Metadata Rejected | You | A metadata-only issue; fix the field and reply, no new build needed. |
If your status is anything other than Waiting for Review or In Review, the ball is in your court — jump to the matching section. Only Waiting for Review that has genuinely exceeded the timing below is a “stuck queue” problem.
Common causes
Ordered by hit rate.
1. The 2026 review backlog
This is the most likely cause right now. App submission volume surged through Q1-Q2 2026, and even trivial updates routinely sit 24-72 hours, with peaks of 5-7 days. Apple’s 90%-in-24h figure is an average across the year, not a guarantee for your specific week.
How to spot it: Check Apple’s System Status page (look for the “Developer ID” / “App Review” rows) and a third-party tracker like appreviewtimes.com. If recent submissions broadly show 3+ days, the delay is system-wide and not about your app.
2. First version of a brand-new app
A brand-new app’s first review includes extra vetting (developer-account history, identity verification, business validation) that updates skip. Expect roughly 2-3x the typical wait for v1.0.
How to spot it: App Store Connect → your app. If this is the first build ever submitted under this app record, build the extra time into your expectations.
3. Submission triggered an automated heuristic
A sensitive entitlement (HealthKit, Contacts access, background modes, location-always), a new authentication scheme (removing Sign in with Apple, adding new SSO), a new in-app purchase or subscription, a child-directed (Kids category) flag, or a category change (for example, entering Medical or Finance) can route the build into extended review.
How to spot it: Diff your current submission’s entitlements.plist, in-app purchase configuration, and category against the last accepted version. Any addition from that list predicts a slower review. Note that subscription/IAP changes are reviewed alongside the binary and can hold the whole submission.
4. Reviewer assigned but waiting on something external
Sometimes the build is effectively under review but the UI lags, or the reviewer escalated to an Apple internal team (legal, privacy) and is waiting on them.
How to spot it: Open Resolution Center and check for any unread reviewer message. If one exists, reply — the clock does not move until you do.
5. Region-specific reviewer pool
China-region submissions, payment-heavy apps, and apps in government-regulated categories can route to a smaller reviewer pool with a different turnaround.
How to spot it: Note your primary target region and the region of the Apple Developer Program account you submitted from. Sensitive regions and mismatches stretch the timeline.
6. Your submission is silently incomplete
Missing export-compliance answers, missing content rights, or an incomplete App Privacy questionnaire can block routing — and in some flows there is no Resolution Center message telling you so.
How to spot it: Open the build and confirm every status indicator is green: Export Compliance answered, Content Rights confirmed, App Privacy complete, Age Rating set. A single Not Set field can hold the whole submission.
Information to collect
- Exact submission timestamp from App Store Connect → your app → App Review (or Activity).
- Current status (from the table above).
- Any Resolution Center messages, including older threads marked as read.
- Whether this is a v1.0 or an update.
- Whether the submission added a sensitive entitlement, new IAP/subscription, or category change.
Shortest path to fix
Step 1: Verify the submission is complete
In App Store Connect → your app → the submitted version, confirm:
- App Information: category set, privacy policy URL valid, contact info present.
- Pricing and Availability: at least one region selected.
- App Privacy: data-collection answers complete, with a recent “Saved” timestamp.
- Export Compliance: answered (encryption Yes/No).
- Content Rights: answered.
- Age Rating: filled per content.
- App Review Information: working demo account, region notes, contact.
Any Not Set or missing field can silently delay routing. Fixing one of these is the only “fix” that can move the status within hours.
Step 2: Check Resolution Center one more time
App Store Connect → your app → App Review → Resolution Center. Open every thread, including resolved ones, and confirm the most recent reply contains no unanswered question. Apple sometimes adds a low-urgency note that pauses the queue without sending an email.
Step 3: Compare against benchmark timing
Use appreviewtimes.com, the Apple System Status page, or developer communities (r/iOSProgramming, Apple Developer Forums) to gauge whether the broader queue is slow. If the recent median is also 3+ days, your delay is the backlog, not your build.
Step 4: Wait the appropriate window (2026 calibration)
These windows reflect the 2026 backlog, not Apple’s best-case figures. Count business days.
| Submission day | Typical wait (2026) | Wait before escalating |
|---|---|---|
| Mon-Wed | 24-72h | 5 business days |
| Thu-Fri | 48-72h | Following Wednesday |
| Weekend submit | 48-96h | Wednesday |
| Known backlog / peak week | 5-7 days | 10-14 calendar days |
Crucial nuance most guides get wrong: editing permitted metadata while Waiting for Review does not requeue you. What does send you to the back of the line is uploading a new binary, submitting a new version, or removing the build from review. So if you are tempted to “do something,” edit a description — never re-upload. (Note: only one submission per platform can be under review at a time, max two total.)
Step 5: Send a polite status request
Once you have passed the wait window, file a request via Contact App Review and choose the status-update topic. Keep it factual:
Submission ID: 12345
App: Acme Studio v2.7
Submitted: 2026-05-15 14:32 PT
Current status: Waiting for Review (6 business days)
Could you confirm whether this submission has been routed?
This release contains a critical fix for [specific user-facing issue].
Thank you.Be factual and specific, no demands. Provide business context only if there is a concrete, dated impact.
Step 6: Request Expedited Review only when truly justified
Use the dedicated form: developer.apple.com/contact/app-store/?topic=expedite (also reachable via “Contact us” at the bottom of App Store Connect). Apple accepts only two reasons: a critical bug fix (include exact steps to reproduce on the current live version) or a time-sensitive event (include the event name, date, and your app’s association). As of June 2026, expedites are being granted less often because of request volume, so reserve it for real emergencies — misuse can suspend the privilege. When granted, expedited reviews typically complete in 6-24 hours.
Attach concrete evidence: a crash-report URL (Sentry, Crashlytics), an App Store review from a user citing the bug, or a press release tied to a date.
How to confirm it’s fixed
- Status moves to In Review, then Pending Developer Release or Ready for Distribution, within hours of escalating or completing a missing field.
- The submission’s history in App Store Connect → App Review shows a state transition with a timestamp.
- An email arrives confirming the review outcome (approval or rejection).
- Subsequent submissions on the same account complete within the typical window.
If it still fails
- Reply on your existing Contact App Review thread with the original case number — do not open a new thread, which loses your history.
- Submit an appeal only if you believe the submission was mishandled (not for plain delays).
- Book an App Review Webex consultation (30 minutes) via Apple’s developer events to ask about a specific entitlement combination known to slow review.
- Ask in r/iOSProgramming or the Apple Developer Forums whether your exact entitlement or category combination is a known slow path.
- Consider shipping the new flagged behavior behind a feature flag (defaulted off) so the next submission has a smaller review surface.
Prevention
- Submit non-urgent updates well before any external launch date — assume 5-7 business days in 2026.
- Keep App Review Information current every time; a stale demo account or missing region note reliably triggers a delay loop.
- Split risky changes (new entitlement, new IAP) from routine bug fixes; a risky bundle slows the entire release.
- Use TestFlight beta review (usually faster) to validate a build before promoting it to App Store review.
- Maintain a release calendar that avoids WWDC week (early June), the week after each major iOS release, and the December holiday window.
FAQ
Will resubmitting the same build make it review faster? No. Removing the build and re-uploading sends you to the back of the queue as a fresh submission. Editing metadata text fields does not requeue you, so if you must act, edit a description — never re-upload the binary.
Is “Waiting for Review” for 5 days normal in 2026? For a routine update it is on the slow side but not alarming during the current backlog; 5-7 days is common for first versions and sensitive categories. Past 7 business days for an update, or 10-14 calendar days for v1.0, is when escalation is reasonable.
Does editing my app’s description or screenshots reset the review? Editing permitted metadata while Waiting for Review does not reset the timer. Screenshots and previews generally cannot be edited once Waiting for Review, and uploading a new binary or removing the build does restart review.
Why is there no Resolution Center message if my app is blocked? Some blocks (missing export compliance, incomplete App Privacy, unanswered content rights) hold routing silently with no message. Re-check that every submission field shows a green status — that is the most common “invisible” cause.
My status is “Pending Developer Release,” not “Waiting for Review” — why isn’t it live? That status means Apple already approved it and is waiting on you. Open the version and click Release this version (or set automatic release). Nothing is stuck on Apple’s side.
Can I see my position in the queue? No. Apple does not publish a queue position, and submissions are not necessarily reviewed in the order received, so there is no slot to “lose” by waiting.
Related reading
- Beta App Review taking too long
- App rejected for Guideline 2.1 — more info needed
- TestFlight build stuck in processing
- App privacy questionnaire rejected
Tags: #Troubleshooting #App Store #App review #app-store-connect