How to Submit an App to the App Store — Complete Guide (2026)

Publishing an app to the App Store should be straightforward. In practice, it is one of the most error-prone steps in the entire iOS development cycle. Certificates expire at the worst moment. Screenshots have pixel-perfect requirements that vary by device. A single metadata field left blank can delay your launch by days. And App Review rejections arrive with cryptic explanations that leave you guessing.

I have submitted dozens of apps to the App Store over the years. Some sailed through review in 24 hours. Others bounced back three or four times before approval. The difference was almost never about the quality of the app itself — it was about how well I prepared the submission.

This guide walks you through every single step of the App Store submission process in 2026, from enrolling in the Apple Developer Program to monitoring your app after it goes live. Bookmark it. You will come back to this one.

Step 1: Enroll in the Apple Developer Program

Before you can submit anything, you need an active Apple Developer Program membership. This costs $99 USD per year (or the equivalent in your local currency). There is no way around this fee — it covers access to App Store Connect, beta testing via TestFlight, advanced app capabilities like push notifications and in-app purchases, and of course the ability to distribute on the App Store.

Individual vs. Organization Enrollment

Apple offers two enrollment types. Choose carefully because switching later is tedious.

• Individual: Your personal name appears as the seller on the App Store. Best for solo indie developers. Enrollment is usually approved within 48 hours. You only need an Apple ID and a credit card.
• Organization: Your company or legal entity name appears as the seller. Requires a D-U-N-S number (free from Dun & Bradstreet, but takes 5-14 business days to obtain). Apple verifies your legal entity, which can add another week. If you plan to use your app commercially under a brand, this is the right choice.

Pro tip: If you do not have a D-U-N-S number yet, request one immediately at dnb.com before continuing with the rest of this guide. The wait time is the longest bottleneck in the entire process.

Enrollment Steps

1. Go to developer.apple.com/programs/enroll
2. Sign in with your Apple ID (or create one)
3. Select Individual or Organization
4. Complete identity verification (Apple may request a video call or government ID scan)
5. Pay the $99 annual fee
6. Wait for Apple to process and approve (24 hours to 2 weeks depending on type)

Once approved, you get access to the Apple Developer portal, App Store Connect, and all the tooling you need to manage certificates, identifiers, and provisioning profiles.

Step 2: Certificates and Provisioning Profiles

This is where most first-time developers get confused. Apple uses a code-signing system to verify that apps come from authorized developers and have not been tampered with. You need two things: a certificate (which proves your identity) and a provisioning profile (which ties your certificate, your app ID, and the devices or distribution method together).

Certificate Types

• Apple Development: Used for running your app on physical devices during development. Limited to your registered test devices.
• Apple Distribution: Used for submitting to the App Store and TestFlight. This is the one you need for release builds.

Creating Certificates in Xcode (Recommended)

The easiest way to manage certificates in 2026 is to let Xcode handle it automatically.

1. Open Xcode and go to Settings → Accounts
2. Add your Apple ID if it is not already there
3. Select your team and click Manage Certificates
4. Click the + button and choose Apple Distribution
5. Xcode will generate the certificate signing request, submit it to Apple, and install the certificate in your Keychain automatically

Provisioning Profiles

For App Store distribution, you need an App Store provisioning profile. Again, Xcode can manage this automatically if you enable Automatically manage signing in your project settings (under Signing & Capabilities). This is the recommended approach for most developers.

If you prefer manual management (for CI/CD pipelines, for example), you can create profiles at developer.apple.com/account/resources/profiles.

# Verify your signing identity from the command line
security find-identity -v -p codesigning

# You should see something like:
# 1) ABCDEF1234... "Apple Distribution: Your Name (TEAM_ID)"

Common gotcha: If you see "No signing certificate" errors, make sure your Apple Distribution certificate is installed in your Mac's Keychain and that the private key is present. If you created the certificate on a different machine, you need to export the .p12 file and import it.

Step 3: Set Up Your App in App Store Connect

App Store Connect (appstoreconnect.apple.com) is the web dashboard where you manage everything about your app's presence on the App Store: metadata, pricing, builds, TestFlight, analytics, and more.

Creating a New App

1. Log in to App Store Connect
2. Go to My Apps and click the + button
3. Select New App
4. Fill in the required fields:
   • Platform: iOS
   • Name: Your app's display name (up to 30 characters)
   • Primary Language: The language for your default metadata
   • Bundle ID: Must match the bundle identifier in your Xcode project (e.g., com.yourcompany.yourapp)
   • SKU: A unique identifier for your app (internal use only, never shown to users)
5. Click Create

Your app now has a record in App Store Connect. The next step is filling in all the metadata fields that determine how your app appears on the store.

Step 4: App Metadata — Title, Subtitle, Description, and Keywords

Your metadata is not just administrative — it is the primary driver of your App Store Optimization (ASO). The words you choose here directly affect whether people find your app and whether they download it after finding it. Take this step seriously.

Metadata Fields and Character Limits

ASO Keyword Strategy

App Store Optimization is the art of making your app rank higher in App Store search results. Here is a practical keyword strategy that works in 2026.

• Research first. Use tools like AppTweak, Sensor Tower, or the free App Store Connect search ads keyword tool to find keywords with decent search volume and manageable competition.
• Put your highest-value keyword in the App Name. If your app is a habit tracker, make sure "habit tracker" appears in the name. This carries the most weight.
• Use the Subtitle for your second keyword. Example: Name = "Streaks — Habit Tracker", Subtitle = "Daily routine & goal planner".
• Fill all 100 characters in the Keywords field. Use commas with no spaces after them. Do not repeat words that already appear in your name or subtitle — Apple indexes those automatically. Do not waste characters on your brand name or common words like "app."
• Think in single words, not phrases. Apple combines words from your name, subtitle, and keyword field independently. So entering fitness,tracker also covers "fitness tracker" as a phrase. Entering the full phrase wastes characters.
• Localize your keywords. If you localize to additional languages, each locale gets its own 100-character keyword field. Even if your app is English-only, setting keywords for the English (UK), English (Australia), and Spanish (Mexico) locales gives you extra indexing opportunities.

Writing a compelling description: Your description does not affect search rankings, but it massively impacts conversion. Lead with the benefit, not the feature. "Wake up feeling energized every morning" beats "Customizable alarm with 30 sound options." Use short paragraphs, bullet points, and social proof (award mentions, download counts, press quotes).

Step 5: Screenshots and App Previews

Screenshots are the single most important conversion factor on your App Store listing. Users decide whether to download in seconds, and your screenshots are what they look at. Apple requires specific dimensions for each device size, and getting these wrong will block your submission.

Required Screenshot Sizes

You can upload up to 10 screenshots per locale per device size. The minimum is 3 for each required size. Here are some rules that will save you from rejection:

• Screenshots must be PNG or JPEG, in RGB color space, without alpha channels
• They must be the exact pixel dimensions listed above — not close, exact
• Do not include any status bar content that implies a different carrier or time (Apple can reject for misleading UI)
• If you add marketing text overlays, keep them honest — do not claim features your app does not have

Screenshot Design Tips That Convert

• Lead with your best screen. The first screenshot is the only one most people see in search results. Make it show the core value of your app immediately.
• Add short, bold captions. Do not rely on the screenshot alone. Add 3-5 word captions like "Track your progress" or "AI-powered recommendations" above or below the device mockup.
• Use a consistent color palette. All screenshots should feel like they belong together. Match your app's design tokens.
• Show real content, not placeholder data. Screenshots with actual data feel more trustworthy than empty states.
• Consider localization. If you support multiple languages, localize your screenshot captions too. This dramatically increases conversion in non-English markets.

App Preview Videos

App Preview videos are optional but highly effective — Apple says apps with previews convert up to 20% better. You can upload up to 3 per locale per device size.

• Format: H.264 or HEVC, 30fps, up to 30 seconds
• Resolution: Must match the screenshot resolution for the device size
• Audio: Optional but recommended. Keep it subtle — many users browse with sound off
• Content: Show actual app footage. Do not use rendered animations or content not in the app — Apple will reject this
• First frame: The first frame is used as the poster image. Make it visually strong

The easiest way to record App Previews is using the Xcode Simulator's screen recording feature or a physical device connected via QuickTime.

# Record simulator screen from command line
xcrun simctl io booted recordVideo preview.mp4

# Press Ctrl+C to stop recording

Step 6: Categories and Age Rating

Choosing Categories

You select a primary category and an optional secondary category. Your primary category determines which top chart your app appears on, so choose strategically. A meditation app could be in Health & Fitness or Lifestyle — check which category has less competition for the top charts in your niche.

Categories available in 2026 include: Books, Business, Developer Tools, Education, Entertainment, Finance, Food & Drink, Games, Graphics & Design, Health & Fitness, Lifestyle, Medical, Music, Navigation, News, Photo & Video, Productivity, Reference, Shopping, Social Networking, Sports, Travel, Utilities, and Weather.

Age Rating Questionnaire

App Store Connect asks you a series of questions about your app's content to determine the age rating. Answer honestly — a mismatch between your declared content and the actual app is a common rejection reason. Key questions cover:

• Cartoon or realistic violence
• Mature or suggestive themes
• Profanity or crude humor
• Alcohol, tobacco, or drug references
• Simulated gambling
• Horror or fear themes
• Medical or treatment information
• Unrestricted web access
• Contests or gambling with real money

If your app has a chat feature, user-generated content, or unrestricted web access, you will likely get a 17+ rating unless you implement robust content moderation.

Step 7: Privacy Nutrition Labels

Since iOS 14, Apple requires every app to declare its data collection practices. These appear on your App Store listing as "App Privacy" cards — often called nutrition labels. Filling these out incorrectly is a growing source of rejections and even post-launch removals.

What You Need to Declare

For each type of data your app collects, you must specify:

• Is it linked to the user's identity? Data tied to an account or device identifier is "linked."
• Is it used for tracking? If you combine user data with third-party data for advertising or share it with data brokers, that is tracking.
• What is the purpose? Analytics, app functionality, advertising, developer advertising, product personalization, or third-party advertising.

Data Categories You Might Need to Declare

• Contact Info: Name, email, phone number
• Identifiers: User ID, device ID
• Usage Data: Product interaction, advertising data
• Diagnostics: Crash data, performance data
• Purchases: Purchase history
• Location: Precise or coarse location
• Health & Fitness: Health data, fitness data
• Financial Info: Payment info, credit score

Do not forget third-party SDKs. If you use Firebase Analytics, it collects device identifiers and usage data. If you use RevenueCat, it collects purchase history and identifiers. If you use AdMob, you are collecting advertising data. Audit every SDK in your project and declare their data collection practices. Apple has started requiring privacy manifests (PrivacyInfo.xcprivacy) from SDKs, so check that your dependencies include one.

Step 8: Pricing and Availability

In the Pricing and Availability section of App Store Connect, you configure:

• Price: Choose from Apple's price tiers or set a custom price. Free apps can add in-app purchases later. Once an app has been free, it cannot be changed to paid (but it can add subscriptions).
• Availability: Choose which countries and regions to distribute in. The default is all 175 territories. You might want to restrict availability if your app is region-specific or if you lack compliance for certain markets (e.g., GDPR for EU, PIPL for China).
• Pre-Orders: You can make your app available for pre-order up to 180 days before release. Pre-orders count toward your day-one download numbers, which can help with chart rankings.

In-App Purchase and Subscription Setup

If your app uses in-app purchases or subscriptions, you must configure them in App Store Connect before submission. Each IAP needs:

• A reference name (internal)
• A product ID (must match the identifier in your code, e.g., com.yourapp.premium.monthly)
• A display name and description for each locale
• A price tier
• A screenshot of the purchase in context (for review)

For subscriptions, you also need to define the subscription group, introductory offers, and promotional offers. If you use RevenueCat, the SDK handles most of the client-side complexity, but you still need to configure the products in App Store Connect.

Step 9: Upload Your Build

With metadata complete, you need to upload your compiled app binary. There are two main approaches: Xcode and the command line.

Method 1: Upload via Xcode (Simplest)

1. In Xcode, select Any iOS Device (arm64) as the build destination
2. Go to Product → Archive
3. Once archiving completes, the Organizer window opens
4. Select your archive and click Distribute App
5. Choose App Store Connect as the distribution method
6. Select Upload
7. Xcode will validate the build, check your signing, and upload it to App Store Connect
8. Wait 15-30 minutes for App Store Connect to process the build

Method 2: Upload via Command Line (CI/CD)

If you use a CI/CD pipeline (GitHub Actions, Fastlane, Xcode Cloud), you can archive and upload from the command line.

# Archive the project
xcodebuild archive \
  -project YourApp.xcodeproj \
  -scheme YourApp \
  -archivePath build/YourApp.xcarchive \
  -destination "generic/platform=iOS" \
  CODE_SIGN_IDENTITY="Apple Distribution" \
  DEVELOPMENT_TEAM="YOUR_TEAM_ID"

# Export the archive to an IPA
xcodebuild -exportArchive \
  -archivePath build/YourApp.xcarchive \
  -exportPath build/export \
  -exportOptionsPlist ExportOptions.plist

# Upload to App Store Connect using altool (legacy) or iTMSTransporter
xcrun altool --upload-app \
  -f build/export/YourApp.ipa \
  -t ios \
  -u "your@email.com" \
  -p "@keychain:AC_PASSWORD"

Note: Apple has been migrating from altool to notarytool and the Transporter app. As of 2026, you can also use xcrun notarytool for upload, or the dedicated Transporter macOS app from the Mac App Store for a GUI-based alternative.

Xcode Cloud

Apple's own CI/CD service, Xcode Cloud, integrates directly into Xcode and App Store Connect. It can automatically build, test, and distribute your app when you push to your Git repository. For solo developers, the free tier (25 hours of compute per month) is usually enough.

Common Build Upload Errors

• ITMS-90717: Invalid Info.plist key. Usually caused by a leftover key from a capability you removed. Check your Info.plist for unused entries.
• ITMS-90283: Missing purpose string. If you use the camera, microphone, location, or other sensitive APIs, you must provide a usage description in your Info.plist (e.g., NSCameraUsageDescription).
• ITMS-90338: Non-public API usage. An SDK you are using calls a private Apple API. Check which framework is causing it and update to a newer version.
• ITMS-90809: Missing privacy manifest. Third-party SDKs must include a PrivacyInfo.xcprivacy file. Update the offending SDK or add the manifest manually.

Step 10: TestFlight Beta Testing

Before submitting for public review, use TestFlight to get your app into real users' hands. This is invaluable for catching bugs, gathering feedback, and building early momentum.

Internal Testing

You can add up to 100 internal testers (members of your App Store Connect team). Internal builds are available almost immediately after processing — no beta review needed.

External Testing

External testing lets you invite up to 10,000 testers via email or a public link. External builds require a brief beta review by Apple (usually 24-48 hours for the first build, instant for subsequent builds in the same version).

TestFlight Best Practices

• Write clear beta release notes explaining what to test
• Create a feedback channel (Discord, TestFlight's built-in feedback, or a Google Form)
• Use TestFlight's crash reports and feedback screenshots
• Run your beta for at least 3-5 days before submitting for review
• Test in-app purchases using sandbox accounts

Step 11: Submit for App Review

Once your build is processed, metadata is complete, and TestFlight testing has given you confidence, it is time to submit for App Review.

1. In App Store Connect, go to your app's version page
2. Select your build from the Build section
3. Review all metadata fields one final time
4. Under App Review Information, provide:
   • Contact information for the reviewer
   • Demo account credentials (if your app requires login)
   • Notes for the reviewer explaining any non-obvious functionality
5. Click Submit for Review

As of 2026, average review times are 24-48 hours, though it can be faster or slower depending on the time of year (expect delays around WWDC, holidays, and major iOS releases).

App Review Guidelines — What You Must Know

Apple's App Review Guidelines are extensive (over 30 pages), but most rejections fall into a handful of common categories. Here is a reference table of the most frequent rejection reasons and how to avoid them.

Handling a Rejection

If your app is rejected, do not panic. Here is the process:

1. Read the rejection message carefully. App Review usually tells you exactly which guideline was violated and often includes a screenshot.
2. Fix the issue. Make the minimum change needed to resolve the rejection. Do not overhaul your app — fix exactly what was cited.
3. Reply in the Resolution Center. If you believe the rejection was a mistake, you can reply directly. Be professional and specific. Reference the guideline and explain why your app complies. Include screenshots or videos if helpful.
4. Resubmit. Upload a new build (if code changes were needed) or resubmit the same build with updated metadata.
5. Appeal if necessary. If you disagree with the review and the Resolution Center conversation is not resolving it, you can file a formal appeal at developer.apple.com/contact/app-store.

Pro tip: Write thorough review notes. If your app has non-obvious features, a login requirement, or anything that might confuse a reviewer, explain it upfront. I have seen apps rejected simply because the reviewer could not figure out how to log in. Provide demo credentials and step-by-step instructions.

Step 12: Release Options

When submitting, App Store Connect asks how you want to release your app once approved. You have three options:

• Automatically release this version: The app goes live as soon as it passes review. Best for most first-time submissions.
• Manually release this version: The app is approved but not released until you click the release button. Useful if you want to coordinate the launch with a marketing campaign.
• Scheduled release: Choose a specific date and time. If the app is approved before that date, it waits. If it is approved after, it goes live immediately upon approval.

For your first app launch, I recommend manually release so you have full control over timing. You can coordinate social media posts, Product Hunt launches, and press outreach to maximize impact.

Step 13: Post-Submission Monitoring

Congratulations — your app is on the App Store. But the work is not over. The first week after launch is critical.

Monitor Crash Reports

Check the Crashes section in App Store Connect and your crash reporting tool (Sentry, Firebase Crashlytics, etc.) daily for the first week. A crash rate above 1% should be treated as an emergency — it affects your App Store ranking and user trust.

Track Key Metrics

• Impressions: How many people saw your app in search results or on the store
• Product Page Views: How many people tapped through to your listing
• Conversion Rate: Product Page Views to Downloads. A healthy rate is 25-35% for most categories
• Day 1/7/30 Retention: If retention drops off a cliff, you have an onboarding or value delivery problem
• Subscription Conversion: For freemium apps, track what percentage of users convert within the first 7 days

Respond to App Store Reviews

Apple lets you reply to user reviews. Reply to every review in the first month, especially negative ones. A thoughtful reply to a 1-star review can sometimes prompt the user to update it. It also signals to potential users that you are an active, responsive developer.

Plan Your First Update

Ship your first update within 1-2 weeks of launch. This demonstrates to both Apple and your users that the app is actively maintained. Include bug fixes, small improvements based on early feedback, and request ratings using SKStoreReviewController.requestReview() after the user has had a positive experience.

The Complete Submission Checklist

Before you hit Submit for Review, run through this checklist:

• Apple Developer Program membership is active
• Distribution certificate and provisioning profile are valid and not expired
• Bundle ID matches between Xcode project and App Store Connect
• Version number and build number are incremented from the previous submission
• App Name (30 chars) includes primary keyword
• Subtitle (30 chars) includes secondary keyword
• Keywords field (100 chars) is fully utilized with no duplicates from the name/subtitle
• Description (4,000 chars) leads with the benefit and has clear formatting
• Screenshots uploaded for all required device sizes (6.7", 6.5", 5.5", iPad if applicable)
• App Preview video included (optional but recommended)
• Age rating questionnaire completed honestly
• Privacy nutrition labels reflect all data collection including third-party SDKs
• PrivacyInfo.xcprivacy manifest is included in the build
• Privacy policy URL is set and publicly accessible
• Support URL is set and functional
• In-app purchases are configured with screenshots for review
• Demo account credentials are provided in the review notes
• TestFlight testing completed with no blocking issues
• No placeholder content, lorem ipsum, or broken links in the app
• All purpose strings (NSCameraUsageDescription, etc.) are present and user-friendly
• Release option (automatic, manual, or scheduled) is selected

How The Swift Kit Makes Submission Easier

If you are using The Swift Kit as your app's foundation, several of these steps are already handled for you. The kit includes a pre-configured project with correct signing settings, a privacy manifest, proper Info.plist entries for common permissions, and a build configuration that is ready for App Store distribution out of the box.

The onboarding templates give you polished screens that screenshot beautifully. The paywall designs are already configured with RevenueCat product IDs that match the recommended App Store Connect setup. And the overall architecture means you spend your time on the features that make your app unique — not on fighting code signing errors or debugging missing entitlements.

Whether you are launching your first app or your tenth, having a solid foundation eliminates entire categories of submission headaches. Check out the full feature list or grab the kit at checkout and focus on what matters — building a great app and getting it into users' hands.