You’ve finished building your iPhone app. The code works. You’ve tested it. Now you need it on the App Store. Most teams mess up at least one step in this process. Here’s the exact sequence to publish without surprises.

Step 1: Prepare Your Marketing Materials

App Icon

• 1024×1024 PNG, no transparency, no rounded corners (Apple applies them).
• Test it against your category’s top apps. It needs to stand out in search results.

Screenshots

• Required sizes: 6.9″ (iPhone 16 Pro Max), 6.5″ (iPhone 14 Plus), 5.5″ (iPhone 8 Plus).
• iPad screenshots required if your app supports iPadOS.
• Use real UI, not marketing mockups. Captions should state outcomes, not feature names.

App Preview Video (Optional)

• 30 seconds max. Show the app doing something impressive in the first 5 seconds.
• No voiceover required. Subtitles recommended.

Step 2: Set Up App Store Connect

Go to appstoreconnect.apple.com. Create a new app record.

You’ll need:

• Bundle ID (must match your Xcode project exactly)
• App name (30 characters max)
• Primary language
• SKU (your internal reference, not visible to users)

Fill in your app’s metadata: name, subtitle (30 chars), description, keywords (100 chars), support URL, privacy policy URL.

Keywords are indexed. Description is not. Put your primary keyword in the name or subtitle. See our ASO guide for the full breakdown.

Step 3: Prepare Your Build

In Xcode:

1. Set your build number higher than the previous submission (App Store Connect rejects duplicates).
2. Set the version number to what you want displayed publicly.
3. Select “Any iOS Device” as the target (not a simulator).
4. Product → Archive.
5. In Xcode Organizer, validate the archive first. Fix any validation errors before uploading.
6. Upload to App Store Connect.

The build takes 10–30 minutes to process after upload. You’ll get an email when it’s ready.

Step 4: Fill Out the Submission Form

Once the build is processed, attach it to your app version and complete:

• App Review Information: demo account credentials if your app requires login, notes for the reviewer explaining anything non-obvious.
• Version Release: automatic (releases immediately after approval) or manual (you trigger it).
• Age Rating: answer the questionnaire honestly. Wrong answers get your app reclassified post-launch.
• App Privacy: declare what data your app collects. Audit your third-party SDKs — they collect data too.
• Export Compliance: most apps qualify for the standard encryption exemption.

Step 5: Submit for Review

Click “Submit for Review.”

First submission: 24–48 hours typical review time. Can be longer during high-volume periods (post-WWDC, early January). Updates typically review faster than new submissions.

You’ll get an email when approved or rejected.

Step 6: If Rejected

Read the rejection reason carefully. Most rejections are fixable — missing privacy disclosures, broken demo account, guideline violations.

Common rejection reasons:

• Guideline 2.1 — App crashes or has bugs. Fix and resubmit.
• Guideline 4.0 — Design issues. Usually UI that doesn’t meet HIG standards.
• Guideline 5.1.1 — Data collection without disclosure. Add privacy labels and permission strings.

Respond through the Resolution Center in App Store Connect. If you disagree with the rejection, you can appeal — but appeals take time. Usually faster to fix and resubmit.

Step 7: After Approval

If you set manual release: go to App Store Connect and release it. If automatic: it’s live. Check it in the App Store within an hour of the approval email.

Set up crash monitoring before launch. Crashlytics (free) or Sentry give you real-time visibility into production issues. Don’t find out about crashes from one-star reviews.

Start collecting reviews with SKStoreReviewRequestAPI after the first successful user interaction. Not on launch. Not on open. After they’ve done something meaningful.

Important Details

• Privacy policy URL is required for all apps.
• If your app uses any Apple APIs that access sensitive data (camera, location, health), you must include purpose strings in your Info.plist. Missing purpose strings = rejection.
• TestFlight builds expire after 90 days. Submit to App Store before your beta build expires if users are depending on it.

Our TestFlight guide covers the beta phase before submission. Our publishing guide goes deeper on the review process itself.

Frequently Asked Questions

How long does App Store review take?

24–48 hours for most apps. Updates are sometimes faster. New apps during high-volume periods (post-WWDC, January) can take longer. Plan for 3–5 days around your target launch date.

Can I update my app after submission but before approval?

Yes. You can cancel a pending submission in App Store Connect and resubmit. This restarts the review clock.

What happens if my app is rejected?

You receive a rejection notice with the specific guideline violated. Fix the issue, resubmit. Multiple rejections for the same issue can trigger an extended review. Read the guidelines carefully before submitting.

Do I need a privacy policy for my iPhone app?

Yes, for all apps. Even simple utilities that collect no user data need a privacy policy URL. Host it somewhere public — a simple webpage is fine.

Can I release my app in specific countries only?

Yes. App Store Connect lets you select which countries and regions your app is available in. You can expand or restrict availability at any time.