App Store submission stuck in Waiting for Review for 3 days
Three days feels long, but the status itself says only one thing: Apple has received the submission and has not started reviewing it. Diagnose the record before changing the build or resetting the queue.
Do not cancel and resubmit solely because the counter reached three days. First confirm every submitted item is still in a review state, check App Store Connect for agreements or compliance actions, and compare the delay with the correct submission type. Contact Apple when the record looks abnormal; reserve expedited review for a critical bug or an event you are directly associated with.
Read the status literally before reading into the delay
Apple defines Waiting for Review as a submission it has received but has not started reviewing. It does not mean a reviewer found a problem, and it does not expose your position in an internal queue.
A three-day wait therefore calls for a record check, not a speculative code change. Capture the submission timestamp, platform, version, and every included item. If an app version, In-App Event, or other item has a different state, the submission-level view can hide the detail that actually needs attention.
Apple also says submissions may not be reviewed in the order they are submitted. Another developer's faster result is not proof that your record was skipped.
Run a ten-minute App Store Connect audit
- Open App Review and inspect the submission, not only the version badge on the app page.
- Verify the intended build is attached and each submitted item still shows Waiting for Review or another expected review status.
- Check Agreements, Tax, and Banking plus export-compliance prompts for an action assigned to your account.
- Confirm the App Review contact details, demo credentials, and backend endpoints are still valid even though review has not begun.
- Write down the exact UTC submission time so future comparisons use elapsed hours rather than calendar-day labels.
Choose wait, contact, or expedite from evidence
Continue waiting when the submission is intact, no account action is pending, and the release is not tied to a qualifying urgent circumstance. Use Apple Developer Support when the status appears inconsistent, an item is missing, or the delay is a clear outlier against comparable submissions rather than a broad headline statistic.
An expedite is a separate decision. Apple names critical bug fixes and launches tied to an event the developer is directly associated with as examples. A marketing date you selected, by itself, is weak evidence. Explain the user impact, immovable date, and why normal scheduling cannot solve the problem.
Avoid the actions that erase useful information
- Do not remove the submission merely to try for a different reviewer.
- Do not upload an unchanged build with a higher build number as a queue-refresh tactic.
- Do not send repeated support requests before new evidence exists.
- Do not describe the wait as an active-review failure; those are different clocks.
If you discover a real blocker in the binary or reviewer access, then removal may be rational. Record why you changed course so the new timeline is not confused with the old one.
Send a support note that can be investigated
Keep the note factual. A reproducible record gives support something to inspect; a demand for approval does not. Never include passwords in the message—keep reviewer credentials in the designated App Review Information fields.
App: [name and Apple ID] Platform/version: [iOS 1.0] Submitted: [UTC date and time] Current status: Waiting for Review Items included: [app version / other items] Checks completed: [build attached, no agreements or compliance actions] Question: Could you confirm whether this submission requires action from our team?
Primary references checked for this guide
Policy statements above are grounded in the linked Apple documentation. Operational recommendations are AppReviewReady's interpretation and should be tested against your app and the current guideline text.
Check the Review Queue Index
Compare queue wait separately from active review time using transparent sample counts.
Open the tool