A rejection from App Review usually feels random. It isn't. Most of them trace back to a short list of causes, and nearly all of those can be found before you hit Submit.
I'm an iOS developer who builds and ships SwiftUI apps, and I review other people's apps before submission. This is the checklist I run. It's in the order I'd work through it, not the order of the guidelines.
1. The app crashes or doesn't work for the reviewer
Guideline 2.1 (App Completeness) is the one people trip on most. The reviewer opens a build on a real device, taps through it, and finds a crash, a dead button, or a screen that says "coming soon."
Before you submit:
- Install the exact build you're submitting through TestFlight, on a physical iPhone, not just the simulator.
- Test on a fresh install with no data, and on a slow or offline connection.
- Remove placeholder text, test content and any feature that doesn't work yet.
- If the app needs a login, give the reviewer a working demo account in App Store Connect. A reviewer who can't get past the sign-in screen can't approve the app.
2. Privacy: what you collect, what you say you collect, and what the app actually does
Privacy is where otherwise good apps get stuck, because three things have to agree: your privacy policy, the privacy answers you give in App Store Connect, and the code.
- Your privacy policy needs a working link, both in App Store Connect and inside the app.
- If you use analytics, ads, crash reporting or any third-party SDK, your privacy answers have to include what those SDKs collect, not just what your own code does.
- If your app lets people create an account, it also has to let them delete that account from inside the app.
- Every permission prompt needs a plain-language reason that matches what the app does with it. "Camera is used to scan box labels" passes. "This app needs your camera" doesn't tell the reviewer anything.
3. Payments and subscriptions
If you sell digital content or features, Apple expects you to use In-App Purchase (guideline 3.1.1). The mistakes I see most:
- A paywall with no way to restore purchases.
- Pricing or trial terms that aren't clear on the screen where the person buys.
- A link or button that sends people to a website to pay for something that should be an In-App Purchase.
- Subscriptions that haven't been tested in the sandbox, including the restore flow.
4. The app doesn't do enough
Guideline 4.2 (Minimum Functionality) is aimed at apps that are a website in a wrapper, or a single screen with little else. If your app could be a bookmark, a reviewer may treat it like one. Native features that make the app worth installing, like notifications, widgets, offline use or device features, help show it earns a place on the home screen.
5. The listing doesn't match the app
Reviewers check the store page against what they see. The usual problems:
- Screenshots that show features the app doesn't have, or that were made for a different version.
- A description that makes claims the app can't back up.
- Keywords in the app name or subtitle that are really about someone else's brand.
- An icon or name too close to an existing app.
This one is cheap to fix and easy to overlook, because you've been looking at your own listing for weeks.
6. Login rules
If you offer other third-party sign-in options, such as Google or Facebook, Apple expects you to also offer a login that limits data collection and lets people keep their email private, such as Sign in with Apple (guideline 4.8). Check the current wording of the guideline before you design your login screen, because Apple has revised it.
What a rejection actually costs
Each round costs days, and the days add up when the same issue is rejected twice because the fix didn't address the real reason. Read the rejection message carefully, answer exactly what it asks, and if it isn't clear, reply in Resolution Center and ask. Reviewers do answer.
A five-minute readiness check
Before you submit, answer these honestly:
- Have I installed this exact build on a real iPhone and used it from a clean start?
- Does a reviewer have everything they need to get past login?
- Do my privacy policy, my privacy answers and my code say the same thing?
- Can someone restore a purchase and delete an account from inside the app?
- Does every screenshot show something the app really does?
If any of those is a "not sure," that's the one to fix first.
If you'd like a second pair of eyes
I do this as a fixed-scope service. App Review is a written, prioritized report on your app before you submit: a guidelines check, a read of your listing and positioning, and a list of what to fix now and what can wait. If you've already been rejected and are stuck on signing, provisioning, TestFlight or the rejection itself, the Submission Rescue offer is built for that.
You can book a free 30-minute call and tell me where your app is. I'll tell you honestly whether you need a review, a rescue, or just an afternoon with the checklist above.
