Special Year-End Offer: AI Review Toolkit $29.99 $49.99 Get it now →

iOS Submission Guide

How to Handle App Store Rejection (And Get Approved Fast)

Getting your app rejected by Apple can feel devastating, but here's the truth: it happens to almost everyone. First-time developers typically face 2-5 rejections before approval. The key is knowing how to respond quickly and effectively.

The Reality Check

Apple rejects over 40,000 apps every week. Even experienced developers rarely pass review on their first submission. The difference between success and failure isn't avoiding rejection—it's how fast you recover from it.


Why Rejections Happen

Based on thousands of developer experiences, most rejections fall into predictable categories. Understanding these patterns helps you prevent them—or fix them faster when they occur.

Tiny Mistakes (Most Common)

"Usually when I get rejected, it's for something tiny I missed in the guidelines." Small oversights in Info.plist, metadata, or purpose strings trigger most first rejections.

Permission Mismatches

Declaring permissions you don't use, or using permissions without proper explanation. Apple's automated scanners catch these instantly.

Crashes & Performance

Apps that crash during review are automatically rejected. Test thoroughly on real devices, especially older models and different iOS versions.

Metadata Issues

Misleading screenshots, incomplete descriptions, missing privacy policy URL, or claiming features that don't exist in the app.

Developer Story: "Apple review team found a typo in a variable name. Instant rejection." — Naval Bihani, Software Engineer

The Recovery Timeline

1

Hour 0-1: Read the Rejection Carefully

Don't panic. Read Apple's rejection message thoroughly. They usually cite specific guidelines (e.g., "Guideline 2.1 - Performance"). Look up that guideline in the official documentation.

2

Hour 1-2: Identify the Root Cause

If the rejection is vague, use the Resolution Center to ask for clarification. Be polite and specific: "Could you please provide more details about which aspect of Guideline X.X we violated?"

3

Hour 2-6: Fix the Issue

Make the minimum necessary changes to address the rejection. Don't refactor unrelated code—this introduces new risks and delays your resubmission.

4

Hour 6-7: Test & Resubmit

Test the fix thoroughly, increment your build number, and resubmit with updated Review Notes explaining what you changed. Reference the original rejection.

Instagram Story: Kevin Systrom received a vague rejection, fixed it the same night, and resubmitted. This act of persistence became part of Instagram's company DNA.

Writing an Effective Appeal

If you believe the rejection was a mistake, or if you've made changes, communicating clearly with Apple can make the difference. Here's the format that works:

// Template for Resolution Center response

Subject: Resubmission for [App Name] - Guideline [X.X] Addressed

Body:

Dear App Review Team,

Thank you for your feedback regarding our submission.

Issue Identified: [Restate the rejection reason in your own words]

Changes Made:

1. [Specific change #1]

2. [Specific change #2]

3. [Specific change #3]

Testing Performed: [Describe how you verified the fix]

Please let us know if you need any additional information or clarification.

Best regards,
[Your Name]

The Danger Zone: Repeated Rejections

Multiple rejections can trigger "Extraordinary Review" status, which significantly extends review times. Here's how to avoid it:

×

Don't resubmit without changes. Simply resubmitting the same build hoping for a different reviewer will flag your account.

×

Don't ignore feedback. Each rejection should result in a visible, documented change.

×

Don't create new developer accounts. Apple tracks this and will ban both accounts.

Do be responsive. Quick turnaround shows good faith and professionalism.

Do document everything. Keep records of all changes made between submissions.

Prevention: Skip the Rejection Cycle

The best rejection is one that never happens. Use this pre-submission checklist to catch issues before Apple does:

Related Guides

Want to Pass on Your First Try?

Our AI Review Toolkit catches the issues that cause rejections before you submit. Don't learn from rejection—prevent it.

Get the AI Toolkit — $29.99

Want AI to audit your app before submission?

Get our AI Review Toolkit with prompts that catch guideline violations automatically.

Get the AI Toolkit