How long does an App Store rejection appeal take?

Most Resolution Center replies arrive within 1–3 business days. If you escalate to the App Review Board, expect 3–7 business days. Apple does not provide SLAs, and complex cases occasionally take longer.

Can I appeal every type of App Store rejection?

You can respond to any rejection through the Resolution Center. The formal App Review Board appeal is reserved for cases where you believe the reviewer made a clear factual error or misapplied a guideline. Spam or duplicate-app determinations (Guideline 4.3) are harder to overturn without substantial evidence of differentiation.

What happens if my appeal is denied?

If your appeal is denied, Apple will typically explain the reasoning. You have three options: modify the app to comply with the cited guideline, resubmit with a different approach, or — in rare cases involving policy disagreements — raise the issue on the Apple Developer Forums where Apple evangelists sometimes engage.

Should I fix the issue first or appeal first?

It depends on the rejection type. If you believe the reviewer misunderstood a legitimate feature, appeal first and provide clarification without making changes. If the feedback is clearly valid and you can fix it quickly, make the changes and resubmit rather than appealing — the appeal process adds days to your timeline.

How to Appeal an App Store Rejection: A Step-by-Step Guide

Getting an App Store rejection notification feels like a gut punch, especially when you've spent weeks or months building your app. The good news: Apple's rejection rate is high (around 40% of first submissions get sent back), and most rejections are fixable. This guide walks you through the exact steps to appeal a rejection, what language actually works, and how to escalate when standard channels aren't enough.

Understanding Why Apple Rejected Your App

Before you appeal anything, read the rejection notice carefully. Every rejection comes with a specific guideline number and a brief explanation in App Store Connect. The most common rejection reasons in 2026 include:

Guideline 4.3 – Duplicate or spam apps
Guideline 4.0 – Design quality issues
Guideline 2.1 – App completeness (demo credentials missing, broken flows)
Guideline 5.1.1 – Privacy policy missing or inadequate
Guideline 2.3.3 – Accurate metadata

Some rejections are clear-cut: you're missing something, or a feature violates a rule. Others are judgment calls — particularly around Guideline 4.3 — where the reviewer may have misunderstood your app's purpose.

Identify which category your rejection falls into before deciding whether to appeal or simply fix-and-resubmit.

Step 1: Open the Resolution Center

The Resolution Center is Apple's official communication channel with the App Review team. You'll find it in App Store Connect:

Go to My Apps and select your app
Navigate to the rejected build (look under the App Review section)
Click View Details next to the rejection
Select Reply to Apple or find the Resolution Center link at the top

The Resolution Center preserves the full conversation history, so every message you send is documented. This matters if you later need to escalate.

Step 2: Write an Effective Appeal Message

The tone and structure of your message significantly affect the outcome. Here's what works:

Be specific, not emotional. Review teams handle thousands of apps. A calm, factual message that directly addresses the guideline cited will always outperform a frustrated one.

Reference the guideline explicitly. Mention the guideline number (e.g., "Guideline 2.1 – App Completeness") and explain, point by point, how your app does or does not relate to it.

Provide evidence. Screenshots, screen recordings, demo credentials, and links to similar apps in the store all help. If your app requires a backend account to demonstrate functionality, provide a pre-populated test account.

Structure your message like this:

Subject: Response to Guideline [X.X] Rejection — [App Name]

Thank you for reviewing [App Name]. We'd like to address the
Guideline [X.X] concern raised in your feedback.

[Clear explanation of the feature or content in question]

[Specific evidence that your app complies, or the
legitimate business reason for the feature]

[If applicable: steps to reproduce the functionality
using the test account below]

Test Account:
Username: reviewer@example.com
Password: AppReview2026!

We believe [App Name] complies with Guideline [X.X] because [reason].
We're happy to provide any additional information needed.

Step 3: Know the Common Rejection Scenarios

Missing demo credentials (Guideline 2.1): Always include a fully functional test account. Don't use placeholder data — the reviewer needs to see the actual user experience, including any paid or premium features.

Design issues (Guideline 4.0): Apple looks for apps that feel polished and purposeful. If this is your rejection reason, consider whether your UI matches iOS Human Interface Guidelines. Sometimes attaching a brief explanation of your design choices helps.

Privacy (Guideline 5.1.1): Your privacy policy must be publicly accessible, cover all data types collected, and be linked in both the app and the App Store listing. Vague policies like "we may share data with third parties" are increasingly rejected.

In-app purchases (Guideline 3.1.1): Any content, features, or subscriptions that could be monetized must use Apple's in-app purchase system. If you're using a non-IAP payment for a legitimate B2B or SaaS scenario, explain this clearly.

Step 4: Escalate to the App Review Board

If you receive a response that you believe is still incorrect, or if your Resolution Center message goes unanswered for more than 5 business days, you can escalate to the App Review Board.

To submit a formal appeal:

Visit developer.apple.com/contact/app-store/
Select Appeal a Rejection from the topic dropdown
Provide your app's Apple ID, the guideline cited, and your full reasoning

The App Review Board is a separate team that reviews escalated cases. They do not simply rubber-stamp the original decision — they conduct an independent review. However, the bar is higher: you need to demonstrate that the original reviewer either misread your app or misapplied a guideline. "I disagree with the guideline" is not a basis for an appeal; "the guideline does not apply in this case because X" is.

Step 5: While You Wait — Should You Resubmit?

If you're confident in your appeal and the fix is small, consider submitting an updated binary alongside your appeal. This doesn't invalidate the appeal process, and if the reviewer agrees with you, the updated build can be approved faster.

If the rejection is complex and your appeal is substantive, wait for a response before resubmitting. Multiple simultaneous submissions can confuse the timeline.

Common Mistakes That Hurt Your Appeal

Generic messages: "Our app is compliant with all guidelines" without specifics is ignored.
Threatening legal action: This escalates the case to Apple's legal department and stops all progress.
Submitting multiple appeals simultaneously: Pick the Resolution Center or the App Review Board, not both at the same time.
Changing the app significantly mid-appeal: Reviewers will need to re-review from scratch, resetting timelines.
Arguing about competitor apps: Pointing out that "App X does the same thing" rarely works and distracts from your case.

When to Give Up and Redesign

Some rejections, particularly around Guideline 4.3 (duplicate apps) and Guideline 4.2 (minimum functionality), may reflect a genuine product problem rather than a reviewer error. If Apple has rejected your app twice for the same reason across two different appeals, the most efficient path forward is usually to redesign the problematic feature rather than continuing to fight.

Read Apple's full App Store Review Guidelines with fresh eyes. You may find that Apple's concern is valid and that a small product change — adding a feature, reworking a UI flow, or removing something — resolves the issue faster than any appeal.

Monitor Your App Store Reviews Automatically

Staying on top of every review is crucial for maintaining your rating and catching issues early. AppStoreReview monitors your app across 175+ countries, sends instant alerts for negative reviews, and lets you set keyword filters — so you never miss a critical review again.

Start monitoring for free →