You've built your iOS app. It works, it looks great, and you're ready to ship. Then you open App Store Connect and reality sets in — certificates, provisioning profiles, bundle identifiers, review guidelines, metadata requirements. Apple's publishing process is thorough, occasionally maddening, and absolutely necessary to navigate correctly. Get it wrong and you face weeks of delays or outright rejection.
This guide walks you through every step of the iOS app publishing process, in order, so you can submit with confidence.
Step 1: Enroll in the Apple Developer Program
You must be an Apple Developer Program member to publish on the App Store. Individual membership costs $99/year. If you're publishing under a company name, enroll as an Organization — this requires a D-U-N-S Number (free to obtain from Dun & Bradstreet, takes 5–7 business days).
Go to developer.apple.com, click "Account," and follow the enrollment flow. Once enrolled, you gain access to App Store Connect, Xcode's cloud signing capabilities, and TestFlight for beta distribution.
Step 2: Configure Your App Identifier
In the Apple Developer portal, navigate to Certificates, Identifiers & Profiles → Identifiers → App IDs. Create a new App ID with a reverse-DNS bundle identifier (e.g., com.yourcompany.appname). This identifier is permanent — changing it later requires submitting a new app. Enable any capabilities your app uses (Push Notifications, Sign in with Apple, In-App Purchases, etc.) at this stage.
Step 3: Create Distribution Certificates and Provisioning Profiles
Certificates cryptographically prove that your app was built by your team. Provisioning profiles link your app ID, team, certificates, and permitted devices together.
For App Store distribution, you need an iOS Distribution Certificate and an App Store Distribution Provisioning Profile. In modern Xcode, you can enable "Automatically manage signing" which handles most of this for you during development. For production distribution, the process is still worth understanding manually.
Step 4: Prepare Your App in App Store Connect
Log into appstoreconnect.apple.com and create a new app. You'll need:
- App name: As it will appear on the App Store (30 character limit)
- Primary language
- Bundle ID: Must match what you configured in Step 2
- SKU: An internal identifier for your records
Step 5: Fill In App Store Metadata
This is more work than most developers plan for. Required metadata includes:
- App description: Up to 4,000 characters. Front-load key features as only the first few lines show before "More"
- Subtitle: 30 characters — appears under your app name in search results, heavily influences ASO
- Keywords: 100 characters total — choose carefully, these drive App Store search algorithm
- Screenshots: Required for every screen size you support. At minimum: iPhone 6.9" (iPhone 16 Pro Max) and iPhone 6.5" sizes. iPad screenshots if you support iPad.
- App preview video: Optional but increases conversion rates significantly — 15–30 second video showing real in-app experience
- Privacy policy URL: Required for all apps
- Support URL
- Age rating: Complete the rating questionnaire honestly
Step 6: Configure In-App Purchases and Subscriptions (If Applicable)
If your app has any paid features, set these up in App Store Connect before submission. Apple takes 15–30% of all in-app purchase revenue. Products must be approved as part of your app review, so incomplete IAP configuration will block approval.
Step 7: Archive and Upload Your Build
In Xcode, set your scheme to "Release" and select "Any iOS Device" as the destination. Go to Product → Archive. Once archiving completes, the Organizer window opens — click "Distribute App," select "App Store Connect," and follow the upload wizard.
"Your first App Store submission will take longer than you expect. Your second will take 30 minutes. The process is learnable — and worth learning correctly."
Step 8: Complete App Privacy Information
Apple requires a detailed privacy nutrition label for every app. You must disclose every type of data your app collects, how it's used, and whether it's linked to user identity. This includes analytics libraries, crash reporting SDKs, and advertising frameworks your app includes. Be thorough — Apple's reviewers check this and misrepresentation leads to rejection.
Step 9: Submit for Review
Before submitting, complete the export compliance questions (does your app use encryption? Most HTTPS-using apps select "Standard Encryption") and review your build in TestFlight with real beta testers. When ready, submit. Most apps receive a decision within 24–48 hours. Apps requiring special capabilities (VoIP, background modes, etc.) may take longer.
Common Rejection Reasons to Avoid
- Crashes or bugs encountered during review (test thoroughly on a physical device)
- Placeholder content ("Lorem ipsum" in screenshots or description)
- Login credentials not provided when app requires sign-in to demonstrate functionality
- Missing privacy policy
- Requesting unnecessary permissions without clear in-app explanation
- Misleading screenshots that don't reflect actual app functionality
- Incomplete or inaccurate privacy nutrition label
After Approval: Planning Your Launch
Approval doesn't mean automatic release. You can set a manual release date, allowing you to coordinate marketing, PR, and social announcements. Consider using App Store's Phased Release to roll out to a percentage of users first — this limits the blast radius if a critical bug surfaces post-launch.
AdaptNXT develops iOS apps and manages the full App Store submission process for clients. Talk to us if you need help navigating publishing or optimising your App Store presence.
