Submitting your first iOS app feels a bit like handing in an exam you weren’t sure you studied for. You click Submit for Review, wait 24 to 48 hours, and hope Apple’s reviewer doesn’t spot the one thing you forgot.
At vrsapp.com, we’ve helped founders push apps live and we’ve seen the same rejections happen over and over. Missing privacy manifests. Broken Sign in with Apple. A screenshot showing a status bar with 67% battery in 2026. Silly things that cost weeks.
This iOS app launch checklist is the one we actually use internally before submission. 27 steps across technical, design, legal and marketing. No fluff, just the blockers that get real apps rejected.
Why Most First iOS Submissions Get Rejected
Apple rejects roughly 30 to 40% of first-time submissions. The reasons are rarely dramatic. They fall into four buckets:
- Guideline 2.1: incomplete app info, crashes, missing demo account
- Guideline 5.1.1: privacy policy issues, missing purpose strings, no account deletion
- Guideline 4.0: design issues, placeholder content, broken links
- Guideline 3.1.1: bypassing in-app purchase for digital goods
If you cover the 27 points below, you’ll dodge nearly all of them.
The Complete iOS App Launch Checklist (27 Steps)
Part 1: Technical Readiness (Steps 1 to 9)
- Build against the latest iOS SDK. As of mid-2026, that means iOS 18 SDK minimum. Apple enforces this for all new submissions.
- Test on real devices, not just the simulator. At least one older device (iPhone 12 or SE 2nd gen) and one recent one.
- Fix all runtime warnings and crashes. Use Xcode’s Organizer and TestFlight crash reports. Zero crashes on launch flows is non negotiable.
- Handle offline states gracefully. Apple reviewers test with airplane mode. If your app shows a white screen, you’re rejected.
- Audit third-party SDK privacy manifests. Since 2024, Apple requires
PrivacyInfo.xcprivacyfor common SDKs (Firebase, Facebook, analytics tools). Missing this triggers an automatic warning at upload. - Implement Sign in with Apple if you offer any other third-party login (Google, Facebook, etc.). Still enforced under guideline 4.8.
- Add all required
Info.plistusage descriptions: camera, photo library, location, microphone, contacts, tracking. Vague strings like “We need your camera” get rejected. Be specific about the feature. - Test push notifications end to end if you use them, including permission prompts and payload handling.
- Verify deep links and Universal Links work from Safari, Messages and Notes.
Part 2: Design and UX (Steps 10 to 15)
- Support all current iPhone screen sizes, including the Dynamic Island layout and the latest iPhone 16 Pro Max resolution. No black bars, no cut-off UI.
- Dark mode support. Not mandatory, but reviewers now flag apps where dark mode is half broken.
- Dynamic Type. Test with accessibility text set to the largest size. Buttons should still be tappable.
- Remove all placeholder content. “Lorem ipsum”, test users named “aaaaa”, and dev-only screens are instant rejections.
- Touch targets minimum 44×44 points. Apple’s Human Interface Guidelines are enforced more strictly than most founders realize.
- App icon in every required size, with no transparency, no rounded corners baked in, and no beta or debug badges.
Part 3: Legal and Privacy (Steps 16 to 20)
- Publish a real privacy policy at a live URL. Not a Google Doc. Not “coming soon”. It must list every data type you collect.
- Complete the App Privacy questionnaire in App Store Connect. Be honest. Apple cross-checks with your SDKs.
- Implement Delete Account in-app if users can create accounts. Enforced since 2022, still a top rejection reason in 2026.
- Terms of Service, especially if you have subscriptions, user-generated content, or handle payments.
- App Tracking Transparency prompt if you or any SDK tracks users across apps. Wording must match Apple’s rules.
Part 4: App Store Connect Setup (Steps 21 to 24)
- Screenshots for every required device size. Currently 6.9″ (iPhone 16 Pro Max) and 6.5″ as fallback. iPad only if you support it.
- Compelling app description and keywords. First 3 lines matter most. Use the 100-character keyword field wisely, no repeats, no competitor names.
- Demo account credentials in the review notes if login is required. Include any codes, OTPs bypass, or special instructions. This alone prevents 20% of rejections.
- Age rating questionnaire completed accurately. Under-rating is a rejection trigger.
Part 5: Marketing and Launch (Steps 25 to 27)
- Landing page live with an App Store badge and a support URL. Apple requires both.
- TestFlight beta with at least 20 external testers for 7 days. Real feedback catches things you missed.
- Launch communication ready: email list, social posts, Product Hunt draft, press kit. You get one launch day, don’t waste it.
Common Rejection Reasons vs. What Fixes Them
| Rejection Reason | Checklist Step | Time to Fix |
|---|---|---|
| Missing demo account | Step 23 | 5 minutes |
| No Delete Account feature | Step 18 | 1 to 3 days |
| Vague purpose strings | Step 7 | 30 minutes |
| Missing privacy manifest | Step 5 | 2 to 4 hours |
| Crash on launch | Steps 2, 3 | Variable |
| Placeholder text visible | Step 13 | 10 minutes |
The Two Week Pre-Submission Timeline
If you want a realistic schedule, this is the one we recommend to founders working with us:
- Week 1: Steps 1 to 15 (technical and design). Ship a stable TestFlight build.
- Days 8 to 11: Steps 16 to 24 (legal, privacy, App Store Connect assets).
- Days 12 to 13: TestFlight external testing, fix bugs.
- Day 14: Final review of the checklist, then submit.
Submit on a Monday or Tuesday. Apple’s review team is faster mid-week and you get more room to react if something bounces.
What to Do If Your App Gets Rejected Anyway
Even with a perfect checklist, rejections happen. Here’s how to handle it without losing a week:
- Read the full reviewer message. They cite the exact guideline.
- Reply in Resolution Center before resubmitting if you disagree. A polite explanation often reverses the decision.
- Fix, don’t argue when the reviewer is right. Ship the fix in a new build.
- Use expedited review only for critical bugs or launch dates. Apple grants it sparingly.
FAQ: iOS App Launch Checklist
How long does Apple’s App Store review take in 2026?
Currently 24 to 48 hours on average for new apps. Updates are often reviewed in under 24 hours. Complex apps or those flagged for manual checks can take up to 5 days.
How much does it cost to publish an iOS app?
The Apple Developer Program costs 99 USD per year. There is no per-app fee. If you sell digital content, Apple takes 15 to 30% commission depending on your revenue tier and program enrollment.
Do I need a company to publish on the App Store?
No, you can publish as an individual. However, publishing as an organization (with a D-U-N-S number) lets you show your company name instead of your personal name, which looks more professional.
What’s the biggest reason first-time apps get rejected?
Incomplete metadata and missing demo accounts, followed by privacy issues (no account deletion, missing privacy manifest, vague purpose strings). Steps 5, 18 and 23 of this checklist prevent the majority of first-time rejections.
Should I launch on iOS or Android first?
iOS first if your target users are in North America, Western Europe, or you’re monetizing early. The review process is stricter but users convert better. Android first if you’re global-first or need faster iteration cycles.
Can I update my app right after launch?
Yes, and you should. Ship a bug-fix update within the first 7 days. It signals to Apple you’re an active developer and improves your standing for future reviews.
Final Word
The iOS app launch checklist isn’t glamorous, but it’s the difference between shipping on your target date and explaining another delay to your team or investors. Print it, share it with your developer, run it as a Notion template. Whatever works.
If you’d rather have someone handle submission for you, that’s exactly what we do at vrsapp.com. Ship with confidence, first try.