You submitted a build for review three days ago and the status in App Store Connect still says Waiting for Review — no transition to “In Review,” no Resolution Center message, no email. Apple’s posted median review time is 24 hours; 90% of submissions clear within 48. When yours is past that window and other teams report normal timing, you need to figure out whether to wait, nudge, or escalate.
The honest answer is: most stuck submissions resolve themselves within 5 business days, and any “fix” you apply (rebuild, resubmit) usually restarts the queue rather than skips it. The right play is to verify your submission isn’t actively waiting on a reviewer question, then wait or escalate based on a calibrated timeline.
Common causes
Ordered by hit rate.
1. High-volume review periods
Apple’s queue volume spikes predictably: the week after WWDC (early June), late November through December (holiday gating + iOS holiday freeze), and the days after a new iOS major release. During these windows, “Waiting for Review” routinely stretches to 4-5 days even for trivial updates.
How to spot it: Check Apple’s review status page and developer communities (r/iOSProgramming, Apple Developer Forums). If others are reporting similar delays, it’s a volume issue, not your submission.
2. First version of a brand-new app
A brand-new app’s first review goes through additional vetting (developer history check, identity verification, business validation) that updates do not. Expect 2-3x the median for v1.0.
How to spot it: App Store Connect → your app → if this is the first build ever submitted, factor in the extra time.
3. Submission triggered an automated heuristic
Adding a sensitive entitlement (HealthKit, ContactsAccess, BackgroundModes), a new auth scheme (Sign in with Apple removal, new SSO), a new IAP, child-directed content flag, or a category change (e.g., entering Medical) flags the submission for extended review.
How to spot it: Diff your current submission’s entitlements.plist, IAP configuration, and category against the last accepted version. Any addition in the lists above predicts a slower review.
4. Reviewer assigned but waiting on something external
Sometimes the build is technically “In Review” but the UI hasn’t updated yet, or the reviewer pinged Apple internal teams (legal, privacy) and is waiting on a response.
How to spot it: Check Resolution Center for any unread reviewer message. If you see one, respond — the clock won’t move until you do.
5. Region-specific reviewer with limited bandwidth
China region submissions, payment-heavy apps, or apps targeting specific government-regulated categories may route to a smaller reviewer pool with different SLA.
How to spot it: Note which region you’re primarily targeting and which Apple Developer Program account region you submitted from. Mismatches or sensitive regions stretch the timeline.
6. Your submission is silently incomplete
Missing export compliance, missing content rights, missing privacy questionnaire — these block routing without a Resolution Center message in some flows.
How to spot it: App Store Connect → your build → ensure all status indicators are green: Export Compliance answered, Content Rights confirmed, App Privacy details complete, Age Rating set.
Information to collect
- Exact submission timestamp from App Store Connect → Activity.
- Current status (Waiting for Review, In Review, Pending Developer Release, etc.).
- Any Resolution Center messages, including older ones marked as read.
- Whether this is a v1.0 or an update.
- Whether the submission included any sensitive entitlements, new IAP, or category change.
Shortest path to fix
Step 1: Verify the submission is complete
In App Store Connect → your app → App Store tab → the submitted version:
- App Information: category set, privacy policy URL valid, contact info present.
- Pricing and Availability: at least one region selected.
- App Privacy: nutrition labels filled, “Saved” timestamp recent.
- Export Compliance: answered (Yes/No on encryption).
- Content Rights: answered.
- Age Rating: filled per content.
- App Review Information: demo account, region notes, contact.
Any “Not Set” or missing field can silently delay routing.
Step 2: Check Resolution Center one more time
App Store Connect → Resolution Center for the app. Click any thread, even resolved ones, and confirm no unanswered question is in the most recent reply. Apple sometimes adds a low-urgency note that pauses the queue without an email notification.
Step 3: Compare against benchmark timing
Use appreviewtimes.com or social media to gauge if the broader queue is slow. If the median across recent submissions is also 3+ days, your delay is system-wide.
Step 4: Wait the appropriate window
| Submission day | Median wait | Wait before escalating |
|---|---|---|
| Mon-Wed | 24h | 3 business days |
| Thu-Fri | 24-48h | Following Tuesday |
| Weekend submit | 36-72h | Wednesday |
| High-volume week | 3-5 days | 7 business days |
Do not resubmit for a different version mid-wait — it restarts the queue.
Step 5: Send a polite status request after 5 business days
If you’ve passed the wait window, file via Contact App Review — pick “Status update on a submission”:
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 issue affecting users].
Thank you.Tone matters: factual, specific, no demands. Provide business context only if there’s a concrete impact.
Step 6: Request Expedited Review only when truly justified
In App Store Connect → Contact Us → Expedited Review. Valid reasons: critical data loss bug, security vulnerability, time-sensitive event (sports, news). Misusing expedites can suspend the privilege.
Provide concrete evidence: a Sentry crash report URL, an App Store review from a user citing the bug, a press release tied to a date.
How to confirm the fix
- Status moves to In Review or Pending Developer Release within hours of escalating or unblocking a missing field.
- Activity log in App Store Connect shows a state transition.
- Email arrives confirming review outcome (approval or rejection).
- Future submissions in the same account complete within median timing.
If it still fails
- Reply to your Contact App Review thread with the original ticket number; do not open a new thread.
- Tag the App Store Developer Relations account on Twitter / X with the submission ID (works occasionally for high-priority issues).
- Ask other developers in r/iOSProgramming whether your specific entitlement combination is known to slow review.
- Consider whether shipping with a feature flag (defaulting the new flagged behavior off) reduces the review surface for next time.
Prevention
- Submit non-urgent updates well before any external launch date — assume 5 business days to be safe.
- Keep App Review Information current across submissions; stale demo accounts or missing region notes guarantee a delay loop.
- Split risky changes (new entitlement, new IAP) from routine bug fixes; each risky bundle slows review for everyone on that release.
- Use TestFlight beta review (faster) to validate a build before promoting it to App Store review.
- Maintain a release calendar that excludes WWDC week, the week after each major iOS release, and the December holiday window.