iOS APP STORE LAUNCH: 7 GOTCHAS NOBODY WARNS YOU ABOUT

Building the iOS app is the easy part. The rest of the launch — Apple's review, entitlements, in-app purchase setup, screenshot prep, TestFlight, age ratings — is where every first-time launch stalls.

Here are the 7 gotchas we plan for in every iOS engagement, because skipping any one of them adds 1–2 weeks to the timeline.

1. THE FIRST REJECTION IS PROBABLY COMING

Apple rejects ~30% of first submissions. Usually for one of: missing privacy strings (NSCameraUsageDescription etc.), test account credentials not provided, a Sign in with Apple option missing when you offer 3rd-party login, or a sandbox-only feature broken in review.

Budget 1 week for the rejection — don't treat it as failure. It's a checklist completion step.

2. IN-APP PURCHASE TAKES TWO ACCOUNTS, NOT ONE

App Store Connect bank account + tax info + agreements have to be fully signed AND active before in-app purchase will work in production. There's a known race: your app gets approved, but purchases return "product not found" because the paid agreements aren't live yet.

Fix: sign all the agreements before you upload the first build, not after.

3. SCREENSHOTS ARE NOT JUST SCREENSHOTS

You need 6 sets minimum: 6.7" iPhone, 6.5", 5.5", 12.9" iPad, 11" iPad, Apple Watch (if applicable). Apple uses the 6.7" set for the others if you don't upload separately — but the crop is wrong often enough that you should make all sizes.

Real labor: ~1 day for design + export. Budget it.

4. TESTFLIGHT REVIEW IS ITS OWN SUBMISSION

The first external TestFlight build needs Beta App Review (1–3 days, usually 24 hours). Subsequent builds with no significant changes don't. But your first "launch your beta to 100 testers!" is a separate review queue from the App Store submission. Many first-timers don't know this and miss their stakeholder demo by a day.

5. PRIVACY MANIFEST IS NEW AND ENFORCED

Since 2024, Apple requires a privacy manifest for many SDKs. If you use any 3rd-party SDK (Sentry, Firebase, Mixpanel, anything), you may need a PrivacyInfo.xcprivacy bundle. Missing one is a silent App Store Connect upload rejection — you get the error in App Store Connect, not in Xcode.

6. AGE RATING IS LITERAL

Apple takes the answers literally. If your app can show user-generated content — chat, comments, anywhere — answer "Yes" to UGC. Skipping it once means a 9+ rating and an instant rejection on the next submission when reviewers notice. We've seen this kill 2 weeks.

7. SUBMITTING ON FRIDAY IS A MISTAKE

App review is fastest Tuesday–Thursday, slowest right before major Apple events (WWDC week, fall launch week). If you submit Friday, your first response often lands Monday or Tuesday. Submit Tuesday morning Pacific time for the best odds.

THE REALISTIC TIMELINE

From "build done" to "app live": 1–2 weeks. Day 1–3: screenshots, app store metadata, privacy + age rating + bank info. Day 4: upload, submit for review. Day 5–7: review (usually 24h, sometimes longer). Day 7+: fix anything rejected, resubmit. Day 10–14: live.

We bake all of this into the iOS app development timeline. The 6–10 week build window includes the launch labor.