Can I appeal an App Store rejection?

Yes. Apple runs an appeal channel called the App Review Board, and you reach it through the developer contact form at developer.apple.com/contact/app-store/?topic=appeal. It is real, it is free, and it is much narrower than most developers assume.

The Board decides whether a guideline was applied correctly to your app. It does not decide whether the guideline is reasonable, and it is not a second opinion from friendlier reviewers.

Apple's own framing, from its App Review page, tells you exactly which door you are knocking on:

"If your app didn't pass review and you feel we misunderstood your app's concept and functionality, or that you were treated unfairly by Apple in the course of our review, you may choose to submit an appeal to the App Review Board."

Two triggers in that sentence: a misunderstanding of what your app is, or unfair treatment. Neither of them is "the rule is annoying".

When appealing is the right move

The reviewer described your app incorrectly. They said it duplicates an existing app, or streams third-party content, or collects data it does not collect. This is the strongest appeal there is, because you are not arguing about a rule. You are correcting a fact, and you can prove it with a screen recording.

The guideline cited does not cover your model. A subscription rejection under 3.1.2 aimed at a business you do not run. A reader-app rule applied to something that is not a reader app. Guideline mismatches happen, and they are exactly what the Board is for.

You were told two different things. Round one asked for X, you shipped X, round two rejected X. An appeal that lays out both messages side by side is a legitimate case about the process rather than the app.

The same citation has come back three times unchanged and the thread has stopped producing new information.

When it is a waste of your week

The rejection is correct and you would rather it were not. If the app really does the thing they named, the appeal is a slower route to the same fix.

You want it to go faster. An appeal is not an expedite. If speed is the problem, fix and resubmit, which is almost always quicker than any appeal.

You want a different reviewer. There is no button for that, and the appeal is not it.

You disagree with the guideline itself. Apple has a separate form for that, and using the appeal channel for policy argument spends credibility you may need later.

You have not replied in Resolution Center yet. Apple asks you to exhaust the thread first, and says so explicitly.

Apple's three rules for filing

Straight from the same page, and worth following literally:

"Provide specific reasons why you believe your app complies with the App Review Guidelines."

"Submit only one appeal per submission that didn't pass review."

"Respond to any requests for additional information before submitting an appeal."

The second one is the trap. One appeal per submission means you get a single shot per rejection, so filing a thin appeal the hour you get the email burns it. Write it properly, once.

The third one is the other trap. If the reviewer asked a question in Resolution Center and you appealed instead of answering, you have skipped a step Apple named.

How to submit one

1. Open developer.apple.com/contact/app-store/?topic=appeal. You will be asked to sign in with the Apple Account attached to your developer membership. The form sits behind that sign-in, so a link shared with a colleague outside the team will not work for them.
2. Identify the app and the specific submission that did not pass. Have the app name, Apple ID (the numeric one), version string and the date of the rejection to hand.
3. Write the case in the free-text field. Detail below.
4. Submit, and note the date somewhere you will see again. Nothing in App Store Connect records that you filed.
5. Keep fixing the app in parallel if a fix exists.

What to write

Treat it as a one-page brief for someone who has never opened your app. Four parts, in this order.

The citation, quoted. Paste the exact rejection text and the guideline number. Do not paraphrase it. Whoever reads the appeal wants to see the words the reviewer used.

What the app actually does, in specifics. Screen names, tap sequences, what happens on the server. "The Export button writes a local file. It does not upload anything, and the app makes no network requests on that screen."

Why that means the guideline is not breached. One paragraph, tied to the guideline's own wording.

Evidence. A screen recording of the exact flow, timestamped in your description. Working demo credentials, again, even if you supplied them before. A link to documentation if a third party's terms are involved.

Then stop. Keep the tone flat and factual. No history of how many days you have lost, no mention of revenue, no comparisons to other apps that got away with it. The person reading did not reject you, and an appeal that reads as a complaint gets read as one.

The honest part

Apple publishes no turnaround time for appeals, no acknowledgement that yours arrived, and no outcome statistics. There is no ticket number, no status page, and nothing in App Store Connect that shows an appeal is open.

That is not a gap in this article. It is the actual state of the channel, and anyone quoting you a number for "how long the App Review Board takes" is repeating a story.

What follows practically:

• Do not build a launch date around an appeal. Build it around a fix, or around holding an approved version in Pending Developer Release.
• Expect silence, then a decision. The first thing you hear may well be the outcome.
• Do not chase it. With one appeal per submission and no queue you can see, a follow-up adds nothing.

Two channels people mistake for the appeal

Guideline suggestions, at developer.apple.com/contact/app-store/?topic=guideline. Apple's description: "Help improve the App Review Guidelines or identify a need for clarity in our policies by suggesting guideline changes." This is where an argument with the rule belongs.

Support for an unresolved rejection or removal, at developer.apple.com/contact/request/app-review/support/. Apple's words: "You can contact us to ask for support with an unresolved app rejection or removal." Lower stakes than an appeal, and it does not consume your one shot.

There is also an App Review appointment: a 30-minute Webex conversation you can book from Apple's events schedule, where you can "ask for advice on what to expect during review, how your app can best align with guidelines, reasons for common rejections". For a repeat rejection you do not understand, that conversation is often worth more than an appeal.

FAQ

Does appealing hurt my chances next time? Apple publishes nothing to suggest it does, and the channel exists to be used. Filing a weak appeal on every rejection is a different matter, since the one-appeal-per-submission rule means you are spending something each time.

How long does the App Review Board take? Apple does not publish a figure and does not acknowledge receipt. Plan as though you will hear nothing for a while, and keep working on the fix.

Can I appeal a Metadata Rejected decision? Yes, the channel is the same. It is rarely worth it, because a metadata objection is usually fixable in a browser in ten minutes and needs no new build.

Is there an appeal for Google Play? Yes, but it works differently: one appeal per enforcement action, and no message thread beforehand.

AppSubmit keeps the rejection text, the guideline number and every reply attached to the version they belong to, which is the raw material an appeal needs and the thing most teams reconstruct from email at the worst moment. The Resolution Center thread holds the same history if you keep it tidy yourself.