TL;DR

• Review timeline: 24–48 hours typical; longer post-WWDC and January
• Top 3 rejection reasons: crashes (2.1), HIG violations (4.0), missing privacy strings (5.1.1)
• Required listing: Name (30 ch), Subtitle (30 ch), Keywords (100 ch), Privacy Policy URL, Support URL
• Required screenshots: 6.9", 6.5", 5.5" iPhone sizes; iPad if supported
• Rule of thumb: never set a hard launch date that depends on Apple approval

Written by the Applefy team — we've published apps to the App Store and dealt with every category of rejection on this list.

Most teams think publishing is the easy part. It's not.

We've seen clients get rejected because a screenshot was the wrong resolution. We've seen apps sit in review for two weeks because the privacy policy URL returned a 404. We've seen $80K builds stall because the bundle ID in Xcode didn't match what was registered in App Store Connect.

This guide covers everything from pre-submission to post-launch monitoring — so you avoid the common traps.

Before You Submit

Read the App Store Review Guidelines

Not optional. Apple's review team references these guidelines in every rejection. Read them at developer.apple.com/app-store/review/guidelines before you submit. Focus on Section 2 (Performance), Section 4 (Design), and Section 5 (Legal).

The most cited sections in rejections we've seen: Section 2.1 (crashes), Section 4.0 (HIG violations), and Section 5.1.1 (missing privacy purpose strings). Read those three first.

Test on Real Devices

Test on at least three device types: the latest iPhone, an older iPhone (SE or 3–4 year old model), and an iPad if your app supports it. The simulator does not catch device-specific rendering issues or performance problems on older hardware.

Verify All Links and Accounts

Every URL in your app must work. Every link in your App Store listing must work. If your app requires login, create a demo account and include those credentials in your submission notes. A reviewer who can't access your app will reject it.

Prepare Your Listing

In App Store Connect:

• Name (30 chars): Include your primary keyword. See our ASO guide.
• Subtitle (30 chars): Your secondary keyword. Indexed by the App Store algorithm.
• Description: Lead with your value proposition above the fold. The first three lines are what most users see.
• Keywords (100 chars): No repeats from name/subtitle. No competitor names.
• Privacy Policy URL: Required for all apps. Make sure it actually loads — Apple checks this before a human reviews the app. A 404 here is an automatic rejection.
• Support URL: Must be a working page where users can get help.

Create and Upload Your Build

1. In Xcode: Product → Archive.
2. Validate the archive in Xcode Organizer. Fix any warnings or errors.
3. Upload to App Store Connect.
4. Wait 10–30 minutes for processing.
5. Attach the processed build to your app version.

Build numbers must be higher than any previously uploaded build. Version numbers are what users see. Increment both appropriately.

Complete the Submission Form

• App Review Notes: Explain anything non-obvious. Test credentials for login-gated features. Instructions for features that require specific setup.
• Age Rating: Answer the questionnaire accurately. Wrong answers get reclassified.
• App Privacy Labels: Declare all data collected, including by third-party SDKs. Lying here gets your app removed.
• Export Compliance: Most apps qualify for the standard exemption.

Submit for Review

Click "Submit for Review."

First-time submissions: 24–48 hours typical. During high-volume periods (post-WWDC, January), can take longer. Updates review faster than new submissions in most cases.

Don't plan a hard launch date that depends on App Store approval. Apple's timeline is an estimate, not a commitment. Build in buffer.

Set up monitoring before the review period ends. Crashlytics or Sentry in production. You want crash visibility on day one, not after your first one-star review mentions it.

App Store Review Timeline

Submission typeTypical review timeWorst caseFirst-time app24–48 hours5–7 daysApp update12–24 hours3 daysPost-WWDC / January+50–100%1–2 weeksExpedited review (rare)~24 hoursN/A

After Submission

You'll get an email for approval or rejection. Check App Store Connect for the status.

If approved and set to manual release: go to App Store Connect and release it. Don't forget this step. Apps that sit in "Pending Developer Release" indefinitely are a common mistake.

If Rejected

Read the rejection reason carefully. Most rejections have a specific guideline violation cited. Fix the cited issue. Don't guess.

Top 5 App Store Rejection Reasons

GuidelineReasonHow to fix2.1Crashes during reviewTest on real devices, fix the crash, resubmit4.0HIG / design violationReview HIG for the cited element, redesign5.1.1Missing privacy purpose stringsAdd NSCameraUsageDescription etc. to Info.plist2.3Inaccurate metadataMake screenshots and description match the app4.2Minimum functionalityMore than a shell — no plain web wrappers

If you believe the rejection is wrong, appeal through the Resolution Center in App Store Connect. Be specific — cite the guideline and explain why your app complies. Vague appeals get ignored. Fixing and resubmitting is almost always faster.

Once Approved

Monitor crash reports for the first 48 hours. Watch for review patterns from early users. Respond to early reviews — users who see you respond are more likely to give you a second chance.

Plan your next update before launch. iOS development that stops after shipping is an app in slow decline. The App Store favors active, regularly updated apps.

Frequently Asked Questions

How long does App Store review take in 2026?

24–48 hours for most apps. Updates are often faster. High-volume periods around WWDC and January can extend this. Plan for up to 5 days around any target launch date.

Can I update my submission before it's reviewed?

Yes. Cancel the pending submission in App Store Connect and resubmit. The review clock restarts.

How do I appeal an App Store rejection?

Through the Resolution Center in App Store Connect. State your case clearly and reference the specific guideline you believe was misapplied. Appeals can take days. Fixing and resubmitting is usually faster.

Can I launch in specific countries only?

Yes. App Store Connect lets you select territory availability. You can expand globally after validating in a smaller market.

What's the most common reason apps get rejected?

Crashes during review (Guideline 2.1) and missing privacy disclosures (Guideline 5.1.1) are the most frequent. Test on real devices. Audit your privacy labels before submitting.