App Rejected by Apple? Steps to Fix and Resubmit
Updated: October 2026
If Apple rejected your iOS app, read the reviewer’s message carefully, reproduce the problem on a real iPhone, fix it, test the whole app again, and resubmit with clear review notes. A rejection is common and fixable. Most developers get at least one.
Step 1: Read the rejection message slowly
Open App Store Connect and read the message in Resolution Center. Note three things:
- The guideline number Apple mentions (for example 2.1 or 5.1.1)
- The exact problem the reviewer describes
- Any screenshots or steps the reviewer included
Do not guess. Fix what the message says, not what you think it means.
Step 2: Reproduce the problem
Install the exact build that was rejected on a real iPhone and follow the reviewer’s steps. If you cannot reproduce it, check these common causes:
- The demo account does not work, or has expired
- Your server was offline or slow during review
- The bug only happens on a fresh install
- The bug depends on a certain iOS version, screen size or network
Step 3: Decide: fix it or reply
- It is a real bug or policy issue: fix it in a new build.
- It is a metadata issue: for example screenshots or description. You may be able to fix it without a new build.
- The reviewer misunderstood your app: reply politely in Resolution Center with a short explanation and, if useful, extra review notes. Stay calm and factual.
Step 4: Fix the problem and test everything again
Fixing one bug can break another. Do not test only the screen you changed. Test the full app on a real iPhone: login, main flows, permissions, purchases and a fresh install.
Step 5: Improve your review notes
Many repeat rejections happen because the reviewer could not understand or reach a feature. Add short, clear notes:
- Demo account email and password
- How to reach hidden or special features
- Anything that needs hardware or a special setup
- What you changed since the last submission
Step 6: Resubmit
Upload the new build, attach it to your version, check that your server is live, and submit again. If you have a real deadline or a critical bug fix, Apple has a way to request an expedited review. Use it only when it is truly urgent, and check Apple’s current rules for it.
Checklist: before you resubmit
- I read the full rejection message
- I reproduced the problem on a real iPhone
- I fixed the exact issue mentioned
- I tested the whole app again, not just one screen
- My demo account works
- My backend is live
- My review notes are clear and updated
How to avoid a second rejection
A second rejection usually means the first fix was incomplete or something else was hiding behind it. Reviewers often find more than one issue over several rounds. Testing the full app before resubmitting is the best protection. Our Pro and Max plans were built for this: you send each fixed build and a tester checks it again by hand on a real iPhone. We cannot guarantee approval, but we help you find the problems before the next review.
Frequently asked questions
How long does it take to get reviewed again?
It usually follows the normal review time. See our guide on how long App Store review takes.
Can I argue with a rejection?
Yes. If you believe the reviewer is wrong, reply with clear facts, or use Apple’s appeal process. Be polite and specific.
Does a rejection hurt my developer account?
A single rejection for a bug is normal. Repeated policy violations can be a bigger problem, so read the guidelines carefully.