sodcalculator

10 Tech How-To

App Store Rejection: How to Reply, Fix & Appeal

Guide 10-51405 · Updated · Step by step

Getting an app store rejection is frustrating, but it’s a normal part of the submission process. This guide walks you through the three paths you can take: replying to the review team with clarifying information, fixing the issue and resubmitting, or filing a formal appeal if you believe the rejection is a mistake. You’ll learn exactly what to write, what to change, and how to escalate without burning bridges.

What You’ll Need

  • Your Apple Developer account login (with App Store Connect access)
  • The App Store Connect app or website
  • The rejection message (copy it to a text file for reference)
  • Your app’s build and version number
  • Any supporting documents: screenshots, video recordings, server logs, or a test account

Step-by-Step

  1. Read the full rejection message. Open the email from Apple or check App Store Connect under “App Review.” The message includes a specific reason code (e.g., 2.1, 3.2, 4.0) and a description. Read it twice. Highlight the exact issue they mention—it’s usually one sentence in the middle.
  2. Identify the type of rejection. There are three common scenarios:
    • Information needed: Apple asks for more details (e.g., a demo account, a privacy policy URL).
    • Bug or crash: The app crashed or didn’t work as expected during review.
    • Guideline violation: Your app breaks a specific App Store Review Guideline (e.g., 4.2 minimum functionality, 5.1.1 data collection).
  3. Decide your response path. For information needed, reply directly. For a bug, fix the code. For a guideline violation, you can either fix the app to comply or appeal if you believe the rejection is wrong.
  4. For information needed: reply in App Store Connect. Go to your app’s “App Review” section, find the rejected version, and click “Reply to App Review.” Write a clear, numbered response. For example: “1. Demo account: test@example.com / password123. 2. The login button is at the top right. 3. The app requires iOS 15.0 or later.” Keep it under 500 words. Attach any files if allowed.
  5. For a bug: fix the code and resubmit. Reproduce the crash if you can. Use Xcode’s crash logs or the device console. Fix the bug, test thoroughly, and upload a new build. Then go to App Store Connect, select the new build, and click “Submit for Review.” In the submission notes, mention: “Fixed the crash on the checkout screen by handling null responses from the payment API. Tested on iPhone 14 and 15 simulators.”
  6. For a guideline violation: fix or appeal. If you can fix it easily (e.g., remove a feature that violates a guideline), do that and resubmit. If you believe the rejection is a mistake, file an appeal.
  7. To file an appeal: In App Store Connect, go to “App Review” and click “Appeal” next to the rejected version. You’ll get a text box. Write a polite, factual argument. State the guideline number, explain why your app complies, and provide evidence. For example: “Guideline 4.2.1 states apps should be useful. Our app is a simple tip calculator, which is a single function. The reviewer said it’s ‘minimal.’ We disagree because it has 3 different calculation modes and a history feature.”
  8. Submit and wait. After replying or appealing, Apple typically responds within 24-48 hours. For resubmissions, the review process restarts and usually takes 1-3 days.

Common Mistakes

  • Being rude or defensive. Apple’s reviewers are human. A hostile reply can get you flagged for “unacceptable behavior” (guideline 5.7). Stay professional.
  • Not providing a demo account. If your app requires login, always include a test account in the reply or submission notes. Without it, they’ll reject again.
  • Replying with a fix description instead of fixing the app. If the app crashes, you must upload a new build. A reply saying “we’ll fix it later” won’t work.
  • Appealing without reading the guideline. If you don’t know the exact guideline, your appeal will sound vague. Quote the guideline text.
  • Resubmitting the same build. If you don’t change anything, you’ll get the same rejection. Always upload a new build with changes.

Tips

  • Use the reply box for clarifications. Even if you’re resubmitting, add a note in the “App Review Information” section explaining what you changed.
  • Include a video if helpful. If the issue is about user experience or a feature that’s hard to explain, record a short screen recording (under 2 minutes) and link to it in your reply.
  • Check your privacy policy URL. Many rejections happen because the link is broken or missing. Make sure it’s a live HTTPS page.
  • Test on a real device. Simulators don’t catch everything. Test on at least one physical iPhone and iPad before submitting.
  • Keep a changelog. Track every rejection and your response. This helps you spot patterns.

Troubleshooting

  • If you don’t hear back after 48 hours: Check your email spam folder. If nothing, log into App Store Connect and look for a status update. If it still says “In Review,” wait another 24 hours. You can also use the “Contact Us” form in App Store Connect, but only after 5 business days.
  • If your appeal is rejected: You can still fix the issue and resubmit. The appeal decision is final, but you can make changes and try again.
  • If the reviewer asks for something you can’t provide: For example, they want a demo account but your app uses single sign-on. Explain in your reply why that’s not possible and offer an alternative (e.g., a temporary guest mode).
  • If you get a “binary is invalid” error: This is a technical issue, not a review rejection. Check your build in Xcode, ensure the correct certificate, and re-upload.
  • If the rejection mentions a crash but you can’t reproduce it: Ask for the crash logs. In your reply, write: “Could you provide the crash logs or the steps you took? I’ve tested on multiple devices but can’t reproduce.” Apple often sends them.

Frequently Asked Questions

Q: How long does an appeal take?
Typically 1-3 business days. Apple’s review team is usually prompt, but complex cases can take a week.

Q: Can I call Apple about a rejection?
No, there’s no phone support for app review. You can only use the App Store Connect contact form or the reply box.

Q: What if I disagree with the guideline itself?
You can appeal, but the guideline is the rule. If you think a guideline is unfair, you can submit feedback via Apple’s developer feedback page, but that won’t affect your current rejection.

Q: Can I resubmit after an appeal is denied?
Yes, you can fix the issue and submit a new version. The denial only applies to that specific appeal.

Q: Do I need to pay a fee to appeal?
No, appeals are free. You already paid the $99/year developer fee.

Q: What’s the difference between a reply and an appeal?
A reply is for clarifications or information. An appeal is a formal request to overturn a rejection. You can do either, but not both at the same time.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →