Common App Store rejections and how to fix them

Apple's rejection message quotes a guideline number. Here's what the most common ones really mean, and what to fix before you hit resubmit.

2.1 App Completeness

The reviewer hit a crash, a broken screen, placeholder text, or couldn't log in. Test every screen on a real device, remove "coming soon" and demo content, and put a working test login in App Store Connect → App Review Information.

4.2 Minimum Functionality

The app looks like a website in a wrapper, or does too little. Add real app value: native navigation, push notifications, offline handling, camera or location features, and make sure it feels built for the phone, not just a shrunken web page.

5.1.1(v) Account deletion

If people can create an account in your app, they must also be able to delete it from inside the app, not just by emailing you. Add a clear "Delete account" option in settings that actually removes their data.

4.8 Login services

If you offer sign-in with a third-party account such as Google or Facebook, Apple also expects an equivalent privacy-focused login option, and Sign in with Apple is the usual answer. Email and password login alone doesn't trigger this rule.

3.1.1 In-App Purchase

Digital content or features unlocked inside the app (subscriptions, credits, premium tools) must use Apple's In-App Purchase. Physical goods and real-world services, like a booked session or a delivery, can use Stripe.

How to respond

• Read the full message in App Store Connect → Resolution Center, including any screenshots Apple attached.
• Fix the real cause, then reply in the Resolution Center explaining what you changed.
• If you think the reviewer misunderstood, reply politely with a short explanation or a video. You don't always need a new build.

Guidelines change. Always check Apple's current App Review Guidelines for the exact wording before you resubmit.