An App Store review status tells you where an app version or submission is in Apple’s workflow and which actions are currently available. The key distinction is this: Ready for Review means your draft is prepared but not sent; Waiting for Review means Apple has received it; In Review means review has started.
Read the status before changing the build or metadata. The right next action may be to finish fields, submit the draft, wait, remove it from review, reply to Apple, or upload a corrected build.
The short version
- Prepare for Submission: the record exists but is incomplete.
- Ready for Review: required metadata is present and the item sits in a draft.
- Waiting for Review: Apple has received the submission but has not started.
- In Review: App Review is reviewing it.
- Unresolved Issues: open Apple’s message before deciding whether to reply or resubmit.
The statuses before Apple receives the app
Prepare for Submission begins when the app record or new version exists and you are still adding information. It is a working state, not a queue.
Use it to complete metadata, screenshots, App Review Information, compliance questions, related items, and the selected build. If the version cannot move forward, find the missing field or blocked dependency instead of repeatedly uploading the same archive.
Ready for Review means you entered the required metadata and indicated that you intend to submit the item for review. Under Apple’s current submission flow, selecting Add for Review adds the version to a draft submission and changes its status to Ready for Review.
Apple has not received the draft yet. Open App Review or Draft Submissions, inspect the items, then select Submit for Review. Apple states this explicitly in Submit an app.
This distinction is easy to miss because “Ready for Review” sounds final. It describes readiness of the draft, not receipt by Apple.
Waiting for Review and In Review
Waiting for Review means Apple received the submission but has not started reviewing it. Apple’s status reference notes that some information remains editable while waiting, but screenshots and app previews cannot be uploaded or edited in this state. You can remove the build from review if a real change is required.
Do not interpret time in this state as a silent rejection. Check the recorded status, email notifications, and App Review messages. Review duration is variable.
In Review means App Review is actively reviewing the app. Avoid changing external dependencies, feature flags, demo credentials, or server behavior unless necessary for service continuity. A reviewer needs the route documented in your submission to remain stable.
If you discover a material defect, decide whether leaving the build in review creates more risk than removing it. A code defect requires a corrected build; a server-side or metadata issue may have a different remedy. Document the cause before acting.
For the sequence leading to these states, see the first iOS app submission guide.
Statuses after review succeeds
An accepted version does not always become available immediately. The next status depends on your release choice.
Pending Developer Release means review is complete and you chose manual release. A user with the appropriate role must release the version from App Store Connect.
Pending Apple Release means Apple is processing the version before it becomes ready for sale. This is not a cue to upload another build unless Apple reports a problem.
Processing for Distribution indicates distribution processing is underway. Ready for Distribution means the version is approved and available according to its configured availability and release settings.
The exact labels and editable actions can change as App Store Connect evolves. Use Apple’s live status table for the current definition rather than relying on an old screenshot.
Statuses that require investigation
Some states identify a concrete block rather than normal queue progress.
Invalid Binary means the submitted build does not meet current binary requirements. Read Apple’s delivery message and correct the build issue. Metadata edits cannot repair an invalid binary.
Metadata Rejected indicates that metadata needs correction without necessarily requiring a new binary. Read the specific message and verify whether the affected field is editable in the current state.
Developer Rejected is a historical label for a version removed from review by the developer in applicable workflows. In the current submission model, Apple also exposes actions to remove a submission or item from review. The operational point is the same: the submission is no longer progressing through review and must be corrected and sent again when ready.
Developer Action Needed means Apple is waiting for you to address an issue or provide information. Open App Review messages; do not guess from the status alone.
Unresolved Issues means the submission has an open review issue. It is a container for the conversation, not a diagnosis. Apple’s message, guideline reference, screenshots, and the reviewed build determine the next action.
Choose the next action from evidence
Use this decision table after a status change:
| Evidence | Next action |
|---|---|
| Required field is missing before submission | Complete the record |
| Version is Ready for Review | Inspect the draft and select Submit for Review |
| Submission is Waiting for Review with no issue | Wait and monitor |
| You found a material code defect | Remove if needed, fix, test, upload a new build |
| Apple asks a factual question | Reply with a concise answer and evidence |
| Public metadata is inaccurate and editable | Correct metadata, then reply or resubmit as required |
| Apple reports a binary or runtime defect | Reproduce, fix, test, and submit a new build |
| Apple appears to have missed supplied access | Verify credentials, then reply with exact steps |
Do not appeal before you understand the issue. An appeal challenges the application of a guideline; it does not substitute for missing credentials or a broken flow.
What to record when the status changes
Keep a lightweight submission log:
- app version and build number;
- items included in the submission;
- status and timestamp as observed in App Store Connect;
- Apple message or notification;
- demo account state;
- changes made after submission;
- next owner and action.
This record prevents a team from replying about build 22 while App Review is holding build 21. It also separates actual Apple messages from assumptions about what a status “probably” means.
Do not turn your observed timing into a promise for another submission. The guide to App Store review time explains Apple’s aggregate statement and why individual reviews can take longer.
Handle Unresolved Issues calmly
Open the message and extract four facts:
- the item and build Apple reviewed;
- the cited guideline or requested information;
- the reproduction steps or screenshot Apple supplied;
- the exact state of the demo account and services now.
Then reproduce the path. If Apple’s observation is correct, fix the responsible layer. If the build works and Apple lacked a necessary step, reply with concise evidence and updated access instructions. If policy interpretation remains disputed after you have supplied the facts, consider the available support or appeal route.
A status does not tell you whether a new build is needed. The location of the defect does.
FAQ about App Store review statuses
Does Ready for Review mean Apple has the app?
No. It means the item has been added to a draft submission. You still need to select Submit for Review.
Can I edit the app while it is Waiting for Review?
Some information remains editable, but the available actions depend on the field and status. Apple’s current reference notes that screenshots and app previews cannot be uploaded or edited while Waiting for Review.
What should I do if the status is In Review for longer than expected?
Check messages and service health, then continue to monitor. Do not infer a rejection from elapsed time alone. Use Apple’s support route if the circumstances genuinely require contact.
Does Metadata Rejected require a new build?
Not necessarily. If the issue is limited to editable metadata, correct that layer. Read Apple’s message because a related mismatch in the binary may still require a build.
What does Unresolved Issues mean?
It means Apple has an open issue with the submission. Open the App Review message to learn the actual cause and requested action.
Conclusion
Statuses are routing information. Ready for Review still needs a final submission; Waiting for Review is a queue state; In Review is active review; Unresolved Issues requires message-level diagnosis.
Your next action is to record the exact version, build, and status before changing anything. Then choose the remedy from the evidence, not the label alone.