App Store rejected your build? Here's the recovery plan.

Most App Store rejections are fixable in days, not weeks. The teams that lose the most time aren't the ones with the hardest problems. They're the ones who resubmit in a rush, without understanding why they were rejected.

The first hour: read, don't react.

Before you touch any code:

• Read the full message in App Store Connect. Open your app, go to the App Review section, and read every line. Reviewers often attach screenshots that show exactly where they got stuck.
• Write down the guideline number. For example, 2.1 or 5.1.1. It tells you which rule you broke, and what Apple expects instead.
• Don't resubmit the same build. If nothing changed, the answer won't either. It just costs you another review cycle.

The usual suspects.

A handful of guidelines cause most rejections:

• 2.1 App Completeness. Crashes, bugs, placeholder text, broken links, or a login the reviewer couldn't get past. If your app needs an account, give them a working demo account.
• 2.3 Accurate Metadata. Screenshots, descriptions or previews that don't match what the app actually does.
• 4.3 Spam. The app looks too similar to others, often because it was built from a template with little changed.
• 5.1.1 Data Collection and Storage. Vague permission messages, collecting data you don't need, or letting people create an account without a way to delete it in the app.
• 3.1.1 In-App Purchase. Unlocking digital content or features without using Apple's in-app purchase.

The first day: fix the cause, not the symptom.

1. Reproduce it. Use a real device and the iOS version the reviewer mentioned. Start from a clean install, the way a reviewer does.
2. Fix the root cause. If a screen crashed, find out why. Hiding the screen usually leads to a second rejection.
3. Check for the same problem elsewhere. Reviewers don't always list everything. If one permission message was vague, check all of them.

If you believe the reviewer misunderstood your app, reply in App Store Connect. Be short and specific: what they saw, what the app actually does, and the exact steps to see it. A short screen recording helps.

Before you resubmit.

• Increase the build number.
• Test a clean install, start to finish.
• Update the App Review notes: what changed, demo account details, and steps to reach any feature that isn't obvious.
• Make sure your screenshots and description still match the app.

If you still disagree.

If you've explained clearly and still think the decision is wrong, you can submit an appeal to the App Review Board. Keep it calm and factual. Use it for genuine disagreements, not as a shortcut past a real fix.

Next time: prevent it.

Almost every rejection above can be caught before you submit. Here's the pre-flight checklist I use before every iOS release.