How to Appeal an App Store Rejection (Resolution Center, Review Board, Timelines)
An App Store review appeal has two paths: reply in Resolution Center or escalate to the App Review Board. Here's when to use each, what to write, and how long it takes.
The Argus Team
Reply Argus
An App Store review appeal has two doors, and walking through the wrong one can cost you a week. Door one: reply to App Review in Resolution Center — the fast, informal path for clearing up a misunderstanding or handing over the demo login a reviewer couldn't find. Door two: file a formal appeal to Apple's App Review Board — the escalation you reach for when you genuinely believe the rejection misreads the guidelines. Most developers grab door two when door one, or a quick fix-and-resubmit, would have solved it in a fraction of the time.
Below: how Resolution Center and the Review Board actually differ, when to appeal versus just fix-and-resubmit, exactly what to write (with a template you can paste and adapt), and realistic timelines. Apple publishes none, so we stick to what developers actually see. One rule underpins all of it: if your rejection cited a specific guideline like 4.3, keep that citation's exact wording in front of you. An appeal lives or dies on how precisely you answer the rule you were actually charged under, not the rejection's general vibe.
Resolution Center vs the App Review Board: what's the difference?
These are two different tools, and knowing which is which saves you the most time. One is a conversation. The other is an escalation. Reach for the escalation only after the conversation fails.
- Resolution Center (the conversation) — built into App Store Connect. Every rejection lands here with the exact guideline(s) cited and the reviewer's note. You can reply in-thread, attach screenshots and screen recordings, and ask clarifying questions. Best for: handing over a demo account the reviewer couldn't reach, correcting a factual misread ("you said the checkout crashes — here's a recording of it working"), or simply asking what specifically to change. Most rejections that feel unfair are resolved right here, without a formal appeal.
- App Review Board appeal (the escalation) — a separate, formal request that argues the guideline was misapplied to your app. You submit it through the appeal form linked from Resolution Center and Apple's App Review contact page. A different team than your original reviewer weighs the case. Best for: a genuine disagreement on interpretation that Resolution Center couldn't settle.
- Suggest a guideline change (the long game) — a distinct option for when you think the *rule itself* is wrong, not how it was applied to you. It won't get your current build approved on any useful timeline, so it's rarely the right lever mid-launch.
Should you appeal or just resubmit?
Here's the counterintuitive part: an appeal is almost always slower than compliance. If you can make the change the reviewer wants without breaking your product, fixing the build and resubmitting usually beats waiting on the Board. Appeals are for the cases where compliance isn't an acceptable option, or where you're genuinely right and there's nothing to fix.
A quick decision rule that keeps you out of trouble:
- Reply in Resolution Center first when it looks like a misunderstanding or missing information — a demo login they couldn't find, a server feature that wasn't live during review, an ambiguous note. Cheapest, fastest, no downside.
- Fix and resubmit when the requested change is small and doesn't compromise your app. Compliance you can live with beats a week of arguing every time.
- File a formal appeal only when complying would break a core feature or your business model, or when you're confident the reviewer misread the guideline and the Resolution Center thread didn't move them.
- Don't do both at once without a plan — resubmitting a changed build can moot your appeal, and firing off an appeal while also resubmitting a compliant build just confuses the record.
A resubmit restarts the review queue
There's no "resume where the reviewer left off." A resubmitted build goes back into the queue, so weigh that clock against the appeal clock. If you're only reworking a rejection to comply, our breakdown of [how long App Store review takes](/blog/how-long-does-app-store-review-take) covers what to expect the second time around.
How do you actually file an App Store appeal?
The mechanics are simple; the argument is the hard part. Here's the order of operations that gives you the best odds and the fewest wasted days.
- 1
Step 1 — Pin the exact guideline
Open Resolution Center and note every guideline number cited, word for word. "Rejected under 4.3(a)" and "rejected under 2.1" are completely different arguments. You're answering the specific rule, not the vibe of the rejection.
- 2
Step 2 — Try Resolution Center first
Reply to App Review with clarification and evidence — a screen recording, the demo credentials, a note explaining what they missed. A large share of "wrong" rejections dissolve here in a day, and you never need the Board.
- 3
Step 3 — Open the appeal form
If the thread stalls and you still disagree, submit an appeal via the link in Resolution Center or Apple's App Review "Contact Us" page and choose the appeal option. This routes to the App Review Board, a different team from your reviewer.
- 4
Step 4 — Make one clean argument per guideline
Quote the guideline, explain why your app already complies, and attach proof. Keep it factual and specific. Emotion and "but competitor X does it" arguments rarely land; a screen recording that contradicts the reviewer's claim does.
- 5
Step 5 — Wait, and don't spam
You'll get a decision by email or in Resolution Center. Double-filing, re-opening the same thread hourly, or escalating on social media doesn't speed it up and can sour the record. One clear appeal, then patience.
What should you write in the appeal? (template)
The Board reads a lot of these, so structure wins. Lead with the guideline, answer it with facts, offer to comply if you're wrong, and end with a specific question. Adapt this:
Subject: Appeal — [App Name] v[X.Y] — Guideline [N.N]
Hello App Review Board,
We're appealing the rejection of [App Name] (v[X.Y], submission ID
[ID]) cited under Guideline [N.N].
The rejection states:
"[paste the reviewer's note, verbatim]"
We believe this is a misapplication of [N.N], for two reasons:
1. [Fact + evidence. e.g. "The flagged screen is gated behind a
subscription App Review can access with the demo account below;
a screen recording showing it working is attached."]
2. [Second concrete point tied to the guideline's actual wording,
not to how the rule feels.]
How to reproduce the intended behavior:
- Sign in with demo@example.com / [password]
- Tap [Feature], then [Action]
- The flow completes as described (see recording).
If we've misread the requirement, we're glad to make a reasonable
change. Could you confirm the specific change under [N.N] that would
bring us into compliance?
Thank you,
[Name], [Company]Tone is a feature of the appeal
The reviewer isn't your enemy and the Board isn't a jury to inflame. Cite the guideline text, attach evidence that speaks for itself, and ask exactly what change would satisfy the rule. A calm, specific appeal that makes the reviewer's job easy gets read carefully; an outraged one gets skimmed.
How long does an App Store appeal take?
Honest answer: Apple publishes no SLA for appeals, so anyone quoting you a firm number is guessing. What developers report in practice is that Resolution Center replies often get a response within a day or so, while a formal Review Board appeal typically runs several days and can stretch past a week for complex or high-stakes cases. Don't build a launch date around a pending appeal — you can't control the clock.
One thing an appeal is *not*: expeditable in the usual sense. Expedited review is a lever for time-sensitive *submissions* like a critical crash fix or a fixed launch date, not for hurrying the Board. If your situation is genuinely urgent, the faster route is usually to comply and request an [expedited review](/blog/expedited-app-store-review) on a clean resubmission rather than to wait on an appeal you can't speed up.
An appeal ends one of three ways: the Board sides with you and your app clears, it upholds the rejection and you're back to complying, or it asks for more information, which is really just the Resolution Center conversation reopening. All three reward a tight, evidence-backed argument over a long back-and-forth.
Guideline 4.3 is the most-appealed rejection for a reason
The "spam / duplicate / minimal functionality" rejection under 4.3 is vague by design and catches a lot of legitimate apps, which is why it's the one developers appeal most. If that's your citation, the appeal has to prove genuine differentiation with specifics, not adjectives — we break down exactly how in [beating a Guideline 4.3 rejection](/blog/app-store-review-guideline-4-3-rejections).
The clock that starts the moment you clear review
What makes a good appeal, boiled down: precise, calm, evidence-based writing that answers the exact thing you were charged with. That skill doesn't retire once your build is approved — it changes audience. The day you go live, a second stream of judgment opens and never closes: your reviews. An appeal is one letter you sweat over for an hour; reviews arrive daily, in every language, for the life of the app, each one a tiny public appeal you're either winning or losing.
Nothing legitimate files an App Store appeal for you — that argument is yours. But the ongoing writing problem, the one that actually shapes your rating, is exactly what [ReplyArgus](/features) is built for. It watches your Apple App Store and Google Play reviews in one inbox and drafts an on-brand reply, in the reviewer's own language, the moment one lands, grounded in your past approved replies and ready for you to approve. The calm, specific tone you brought to the Board reaches every user too, without you babysitting two stores. A strong reply reads like this:
Loved the last version but the new update broke offline mode — nothing loads without wifi now. Really frustrating for a commute app.
You're right, and that one's on us — the 3.2 update introduced a caching bug that wiped offline content on commute-heavy routes. We shipped a fix in 3.2.1 (live now) that restores offline mode and re-caches your saved routes automatically. If anything still won't load after updating, reply here with your route and I'll dig into it personally. Thanks for flagging it clearly enough for us to reproduce fast.
That reply does the same job as a good appeal: it names the specific problem, states the fix with a version number, and offers a concrete next step instead of a defensive shrug. Sent within hours instead of days, it's often the difference between a two-star that sticks and a two-star the user quietly bumps to four. When the inevitable angry one-star does land during launch week, here's [how to respond to negative app reviews](/blog/how-to-respond-to-negative-app-reviews) without making it worse.
Frequently asked
- What is an App Store review appeal?
- It's the process for disputing an App Store rejection. You have two paths: reply to App Review in Resolution Center for a fast, informal fix (missing demo info, a factual misread), or file a formal appeal to Apple's App Review Board when you believe the rejection misapplied the guidelines. The Board is a different team from your original reviewer.
- Should I appeal or just resubmit my app?
- Resubmit if you can comply without breaking your product; it's usually faster than an appeal. Reply in Resolution Center first if it looks like a misunderstanding. Only file a formal appeal when compliance isn't acceptable or you're confident the reviewer misread the guideline and the conversation didn't move them.
- How long does an App Store appeal take?
- Apple publishes no official timeline. In practice, Resolution Center replies often get a response within about a day, while a formal Review Board appeal typically takes several days and can exceed a week for complex cases. Don't plan a launch date around a pending appeal, and note that appeals can't be expedited the way submissions can.
- Where do I file an App Store appeal?
- Start in Resolution Center inside App Store Connect, where every rejection appears with the cited guideline. If replying there doesn't resolve it, submit a formal appeal through the appeal link in Resolution Center or Apple's App Review "Contact Us" page, which routes your case to the App Review Board.
- Can I appeal a Guideline 4.3 rejection?
- Yes, and 4.3 (spam / duplicate / minimal functionality) is one of the most-appealed rejections because the rule is broad. To win it, your appeal has to demonstrate genuine differentiation with specifics — unique functionality, distinct content, a real use case — rather than just asserting your app is original. Vague claims of originality tend to fail.
- Can appealing hurt my chances with Apple?
- A single, factual, well-argued appeal won't count against you — the Review Board exists for exactly this. What can hurt is spamming the form, re-opening the same thread repeatedly, or crying wolf. Keep it to one clear appeal per rejection, back every claim with evidence, and offer to comply if you turn out to be wrong.
Bottom line: try Resolution Center before the Review Board, resubmit when you can comply, and save the formal appeal for the cases where you're genuinely right or compliance would break your app. Write it like the template above — one argument per point, evidence attached, a specific question at the end. Then get ready for the writing that never stops. [Start free with ReplyArgus](/signup), no card, and the day your app clears review, Argus pulls every App Store and Google Play review into one inbox and drafts your reply on the spot, so the tone you brought to the Board reaches every user, in their language, in minutes instead of days.
Try it
Let Argus draft your next reply.
Watch it answer a real review in your voice. 10-day trial, no card to begin.
Keep reading
App Store Reviews Not Showing? The Full Fix List for Apple and Google Play
App Store or Google Play reviews not showing? Here's every real cause — moderation delay, wrong country storefront, filtering, rating lag, cache — and the fix.
Read moreAre App Store Reviews Fake? How to Spot Them and What to Do
Yes, some App Store and Google Play reviews are fake — but fewer survive than you think. How to spot them, and what to do when they hit your app.
Read more