How to appeal an app store rejection.
The 2026 playbook.
Your build came back rejected. The message looks final, but it is the start of a conversation. This is how to appeal an app store rejection the right way: reply to the reviewer in the Resolution Center for a fix or a misunderstanding, or file a formal appeal to the App Review Board when you think the decision was wrong. Steps first, no busy work.
The short answer
Two paths, and which to pick.
Apple gives you two ways to respond, and the rejection message tells you which one fits. Knowing how to appeal an app store rejection is mostly knowing which door to walk through, then doing it cleanly.
Reply in the Resolution Center
For a requested change or a misread feature. Write back to the reviewer, attach screenshots or a video, and resubmit. Apple notes replies generally arrive within 24 hours. This clears most rejections.
Appeal to the App Review Board
For a decision you believe is a mistake. Explain how the app complies with the cited guideline. One appeal per submission, so make the case complete. The board replies when its review is done.
Start with Path 1. It is faster, and a clear reply resolves the bulk of rejections without escalating. The rest of this guide on how to appeal an app store rejection walks both paths in order.
The appeal, at a glance.
Reply in the Resolution Center, or appeal to the App Review Board
Apple notes Resolution Center replies generally arrive that fast
You get a single formal appeal per submission, so make it count
You own the React Native, so a requested fix ships the same day
Before you reply
First, read the rejection message.
The reviewer’s note in the Resolution Center is the most useful thing you have. It names the specific guideline they applied and usually describes what they saw or could not reach. Read it in full before you type anything. Half of all confusion about how to appeal an app store rejection comes from skimming the headline and missing the line that says exactly what to fix.
The note also decides your path. If it asks for a change you can make, or if it describes a feature working differently than it does, that is a Resolution Center reply. If you read the cited guideline and your app genuinely complies, that is a candidate for a formal appeal. The wording tells you which.
One more thing worth doing before you respond: this guide is the appeal workflow, not the list of reasons a build gets turned down. If you are still working out why the rejection happened, the companion guide on why apps get rejected from the App Store covers the common causes. Come back here once you know what the reviewer is pointing at.
Path 1
Reply in the App Store Resolution Center.
This is the path you will use most. The Resolution Center is the thread inside App Store Connect where the reviewer explains the rejection and where you write back. Four steps take you from the rejection note to a resubmission.
- 1
Open the rejection in the Resolution Center
Every rejection opens a message thread in App Store Connect called the Resolution Center. Open it and read the whole note, headline and detail both. The reviewer names the guideline they applied and usually describes what they saw or could not do. That text is your brief: it tells you whether this is a fix you make and resubmit, or a decision you disagree with and want to appeal.
- 2
Reply with specifics, not a general defense
Write back to the reviewer in plain, factual terms. Point at the cited guideline, describe exactly what you changed or how the feature actually works, and answer any question they asked. Skip the long apology and the broad argument about your app's value. A reply that says what you did and where to look reads faster and moves the conversation along.
- 3
Attach screenshots, a video, or a document
If the reviewer missed a screen or a flow, show it. The Resolution Center lets you attach screenshots, a short screen recording, or a supporting document. A 20-second video of the exact path they could not find often settles a rejection in one round, because it removes any guesswork about whether the feature exists and works.
- 4
Resubmit, then watch for the reply
Once you have addressed the issue, resubmit from App Store Connect. If your change needed a new build, upload it and submit that version; if it was metadata only, you can update the listing without a new binary. Apple notes that Resolution Center replies generally arrive within 24 hours, so keep an eye on the thread and answer any follow-up the same day.
When a Resolution Center reply is the right move
- The reviewer asked for a change you can make, like a permission string
- A feature was hidden behind a login, a purchase, or a server toggle
- Metadata was off: a screenshot, a description, or a privacy detail
- The fix is small and a quick resubmission is faster than an argument
Apple documents the reply flow in its guide to replying to App Review messages.
Path 2
Appeal to the App Review Board.
When you believe the rejection was a mistake rather than something to fix, you file a formal appeal to the App Review Board. The board re-examines the decision against the guideline that was cited, so your job is to explain, clearly and point by point, how your app complies with that exact rule. You get one appeal per submission, so write it as if it is your only shot, because it is.
Keep it factual. Name the guideline, quote the relevant line if it helps, and map each part of it to what your app actually does. Attach the same evidence you would put in a Resolution Center reply: screenshots, a short video, a document. Separately from an appeal, you can also suggest a change to a guideline or dispute one you think is being misapplied; that is a different track from contesting the decision on your specific build.
On timing, be realistic. The board responds when its investigation is complete, and Apple does not publish a fixed turnaround for appeals, so there is no day count to promise yourself. Apple lays out the process on its App Review page.
Appeal only when this is true
- You read the cited guideline and your app genuinely complies with it
- The reviewer's note describes behavior your app does not actually have
- A Resolution Center reply did not resolve a clear factual disagreement
- You can explain, point by point, how the app meets the guideline's intent
If instead the reviewer asked for a change you can make, do not appeal. Make the change and reply in the Resolution Center; it is faster and it is what the board would point you back to.
Give them this
What reviewers need from you.
A reviewer can only approve what they can see working. A large share of rejections come down to a tester who could not reach the feature, not a feature that was missing. Hand them the keys up front and you remove the most common reason a resubmission stalls.
- A working demo account: a real username and password that reaches a populated account, tested in a fresh install
- Review notes that spell out any non-obvious configuration or the steps to reach a gated feature
- A short video when a flow is hard to find or only appears after a purchase or a toggle
- A clear pointer to the exact screen or action tied to the guideline the reviewer cited
The demo account is where most resubmissions live or die
Give the reviewer a real username and password that lands in a populated account, then test it yourself in a fresh install before you resubmit. If sign-in uses a one-time code, social login only, or a magic link, write a workaround into the review notes so the reviewer is never stuck at the door. A login that fails for them is its own rejection, and it is the easiest one to avoid.
When it is urgent
If it is urgent: request an expedited review.
For genuinely time-sensitive situations, Apple lets you request an expedited review. The two cases it is meant for are a critical bug affecting current users and a time-sensitive event your release is tied to, like a launch dated to a conference or a holiday. An expedited request asks Apple to move your submission up the queue. It does not change the decision, so it pairs with a Resolution Center reply rather than replacing it.
Use it honestly and rarely. It exists for real urgency, not ordinary release pressure, and leaning on it for routine builds tends to wear out its usefulness. When the underlying issue was a misunderstanding and the clock matters, knowing how to appeal an app store rejection quickly comes down to one move: an expedited pass plus a clear, specific reply is often all it takes to clear the rejection.
Where Newly fits
How Newly helps you resubmit faster.
Be clear about the line first: Apple decides whether your app is approved, and Newly cannot influence that decision. You write the Resolution Center reply or the App Review Board appeal yourself inside App Store Connect. What Newly changes is the work on your side of that line, which is where most of the delay in a resubmission actually sits.
Two parts help. First, Newly generates the App Store screenshots, the listing metadata, and a launch video, the assets reviewers often ask to see, so they are ready when you reply rather than a scramble. Second, because Newly hands you real React Native and Expo code that you own, a reviewer’s requested fix is a change you can make and ship the same day. Need to add a permission string, adjust a flow, or wire up the native feature they flagged? Prompt the AI or edit the code, rebuild, and resubmit.
Newly is a paid AI app builder. The Agent 25 plan is $25 a month and includes 50 credits, iOS and Android store deployment, simulators, and the App Store screenshot, metadata, and launch-video generation mentioned above. Top-ups and an Agent 50+ plan add more when you need it. It speeds up your half of the appeal, not Apple’s.
FAQ
How to appeal an app store rejection, answered.
There are two paths, and the rejection message tells you which one fits. If the reviewer asked for something or misread how a feature works, reply in the App Store Resolution Center: explain the change, attach screenshots or a short video, and resubmit. Replies generally arrive within 24 hours. If you believe the rejection itself was a mistake, file a formal appeal to the App Review Board and explain how your app complies with the specific guideline that was cited. You get one appeal per submission, so make the case complete the first time. Most developers start with a Resolution Center reply and only escalate to the board if that conversation stalls.
Fix it and resubmit with Newly.
From $25 a month, Newly generates the screenshots, metadata, and launch video reviewers ask for, and hands you the React Native and Expo code to make a requested fix and ship the same day. You manage the appeal in App Store Connect; Newly clears the work around it.