The App Store appeal letter: when to fight, and how to write it
Appeal to the App Review Board only when the reviewer misapplied a guideline to facts you can prove — for example citing 3.1.5 licensing you already documented, or 4.3 duplication against an app you can differentiate with evidence. If the rejection is factually correct, an appeal wastes 1–2 weeks; build the missing documents and resubmit instead.
Appeal or resubmit? The 30-second decision rule
| Situation | Right move | Why |
|---|---|---|
| Rejection cites missing licensing docs — and you never attached any. | Resubmit with the evidence pack | The reviewer is right. Appeals can't fix missing documents. |
| You attached a mapped legal opinion; the rejection repeats the same form text. | Appeal (or Resolution Center reply first) | The reviewer likely didn't process the evidence — that's reviewable. |
| 4.3 duplicate-app citation, but your entity, brand and features are demonstrably distinct. | Appeal with a differentiation memo | Misapplied guideline against provable facts. |
| Rejection is vague; you're not sure what's missing. | Neither yet — diagnose first | Appealing blind burns your one escalation on a guess. |
Sequence matters: Resolution Center reply → resubmission → App Review Board appeal. Escalate one step at a time; each level reads the record of the one below.
The appeal letter, annotated
1 · Identification. App name, Apple ID, version, date of rejection, guideline cited (3.1.5).
2 · The reviewed facts. "Our submission of ██/██ included Legal_Opinion.pdf (region analysis, section 3) and Country_Availability_Statement.pdf covering all XX storefronts of availability."
3 · The precise disagreement. "The rejection states that no licensing documentation was provided. The attached record shows this documentation was included and maps each region of availability to its legal basis."
4 · The narrow request. "We respectfully request the Board review the attached documentation against Guideline 3.1.5 and confirm whether any specific region or document remains insufficient."
5 · Attachments list. Same filenames as the submission — no new, unexplained documents.
What kills appeals
- Arguing policy. "Other exchange apps are live on the store" has never won an appeal. The Board reviews your record against the guideline, not the market.
- New promises instead of existing evidence. "We will fix this later" concedes the rejection was correct. Appeal only what was already true at submission time.
- Emotion and volume. Multi-page grievances get summarized down to nothing. One page, four blocks, filenames.
- Appealing to buy time. The review clock doesn't pause in your favor, and a denied appeal hardens the record for the next submission.
On the fence? Send the rejection email and your submission record — we'll tell you free whether this is an appeal case or a documents case.
Get the appeal-or-resubmit call →Evidence that must ride with the appeal
Frequently asked questions
How long does an App Review Board appeal take?
Typically several business days to two weeks. That's why the decision rule matters: if the rejection is factually right, building documents and resubmitting is usually faster than appealing.
Does appealing hurt my developer account?
A good-faith, evidence-based appeal doesn't. What damages the record is repeated near-identical resubmissions and unsupported argument — both read as non-compliance patterns.
Can I resubmit while an appeal is pending?
You can, but it usually moots the appeal. Choose the track deliberately: appeal to correct a misapplied review, resubmit to add what was missing.
The appeal was denied — now what?
Treat the denial as a specification: it tells you what the Board considered insufficient. Rebuild the evidence pack around exactly that gap and resubmit. This is the core of what CexPass does.