ShipForge
Sign in
Run Free Launch Score
Blog

App Store Connect Setup (2026): Complete Step-by-Step Guide

· 9 min read

App Store Connect is the control panel for your iOS app. It is where you create your app record, manage signing certificates, fill in privacy disclosures, upload screenshots, set pricing, and submit for review. For a first-time publisher, the setup is the single most common source of delay — not because it is hard, but because there are many steps and skipping one blocks everything downstream.

This guide covers the complete App Store Connect setup for a new app, in the order you should do it, as of 2026.

Prerequisites

Before you touch App Store Connect, you need (Apple Developer Program):

  • An Apple Developer account (Individual or Organization). The Individual plan costs $99/year. Organization accounts require a D-U-N-S number.
  • A Mac with Xcode 15 or later installed.
  • Your app's bundle identifier registered in the Apple Developer portal.

If you are publishing as a company, use an Organization account. Individual accounts work for solo developers but cannot set up multiple team members or use certain enterprise features.

Step 1: Create your app record

In App Store Connect, go to My Apps > New App. You need (Apple Developer):

  • Platform — iOS, iPadOS, or both.
  • Name — The app name shown on the App Store. Must be unique. If your name is taken, you will need a different one.
  • Primary language — The language used for your default app metadata.
  • Bundle ID — Must match the bundle identifier in your Xcode project. You cannot change this later.
  • SKU — An internal identifier for your own use. Not shown to users.

The bundle ID is the one field you cannot change after creation. Double-check it matches your Xcode project exactly.

Step 2: Certificates and provisioning profiles

Your app must be signed with a valid distribution certificate and a provisioning profile. Xcode handles this automatically with "Automatically manage signing," but you should understand what is happening (Apple Developer):

  • Distribution certificate — Identifies you as the developer. Created in the Apple Developer portal or through Xcode.
  • Provisioning profile — Links your distribution certificate to your bundle ID. Tells iOS that your app is allowed to run on devices.
  • App ID — A combination of your team ID and bundle identifier. Must be registered before you can create a provisioning profile.

If you see "No profiles for [bundle ID] were found" in Xcode, it means the provisioning profile has not been created yet. Switch to Automatically manage signing and let Xcode create it, or create it manually in the Apple Developer portal.

Step 3: App information

Under App Information, fill in:

  • Category — Primary and secondary. Choose the category that best describes your app's function. This affects where your app appears in the App Store.
  • Content rights — If your app uses third-party copyrighted material, declare it here.
  • Age rating — Answer the age rating questionnaire. Your answers determine the minimum age for your app.
  • Privacy policy URL — Must be a publicly accessible URL. Not behind a login. Apple checks this.

Step 4: Privacy disclosures (App Privacy)

Since 2020, Apple requires every app to declare what data it collects and how it is used. This is separate from your privacy policy (Apple Developer).

You must declare:

  • Data types collected — Identifiers, usage data, diagnostics, location, contacts, photos, etc.
  • Purpose of collection — Analytics, product personalization, app functionality, third-party advertising, etc.
  • Whether data is linked to the user — Can the data be traced back to the user's identity?
  • Whether data is used for tracking — Does the app use the data to track user activity across other companies' apps and websites?

For AI apps: if you send user prompts to an LLM API, that is data collection. You must declare it. If you store conversation history, that is data linked to the user. Be accurate — Apple has started rejecting apps with incomplete or inaccurate privacy declarations.

Step 5: App review information

Under App Review Information, provide:

  • Demo account credentials — If your app requires login, provide a working demo account. Apple's reviewers will test the full flow. This is the most common reason for rejection under Guideline 2.1(a).
  • Notes — Anything the reviewer needs to know. If your app requires a specific setup, explain it here.
  • Review contact — Name, email, and phone number of the person Apple can contact during review.

Step 6: Screenshots and app preview

Upload screenshots for every device size you support. Apple requires screenshots for:

  • 6.7" display (iPhone 15 Pro Max)
  • 6.5" display (iPhone 14 Plus)
  • 5.5" display (iPhone 8 Plus)
  • 12.9" display (iPad Pro, if supporting iPad)

You can use the same screenshots for multiple sizes if the aspect ratio matches, or generate them from a single 6.7" source using tools like fastlane.

Screenshots must show actual app UI. Apple rejects screenshots that do not match the submitted app.

Step 7: Build upload

Archive your app in Xcode (Product > Archive), then distribute via App Store Connect. Xcode uploads the build, which then appears under the Builds section of your app record.

Once the build appears (usually within 10-30 minutes), select it under the version you are submitting. You cannot submit for review without selecting a build.

Step 8: Pricing and availability

Under Pricing and Availability:

  • Choose whether your app is free or paid.
  • If paid, select a price tier. Apple handles currency conversion.
  • Select the countries where your app will be available.
  • If you offer in-app purchases, set them up separately under In-App Purchases.

Step 9: Submit for review

Once every section has a green checkmark, click Submit for Review. Apple's review team typically responds within 24-48 hours for new apps, though it can take up to 5 days during busy periods.

If your app is rejected, Apple will send a detailed message explaining which guideline was violated. Fix the issue, upload a new build, and resubmit.

Common App Store Connect mistakes

  • Missing demo account — The reviewer cannot get past your login screen. Provide credentials.
  • Incomplete privacy declarations — You forgot to declare that your app collects analytics data.
  • Wrong bundle ID — You cannot change it after creating the app record. Verify before submitting.
  • Screenshots that don't match — You uploaded mockup screenshots that don't reflect the actual app UI.
  • Privacy policy behind a login — Apple cannot verify it. Host it publicly.

How ShipForge helps

ShipForge's free Launch Score includes a check for App Store Connect readiness — verifying you have a demo account, privacy declarations, and public privacy policy before you submit.

Run your free Launch Score at shipforgeai.dev/free-tools/launch-score.

Frequently asked questions

How do I set up App Store Connect for my app?

To set up App Store Connect: enroll in the Apple Developer Program ($99/year), create a new app record in App Store Connect, fill in app information (name, bundle ID, primary language), configure app privacy details, create screenshots, write your description, and submit for review.

How much does an Apple Developer account cost?

An Apple Developer Program membership costs $99 per year for individuals and $99 per year for organizations. This gives you access to App Store Connect, beta testing via TestFlight, and the ability to publish apps to the App Store.

What is a bundle ID and how do I choose one?

A Bundle ID uniquely identifies your app on Apple platforms. Use reverse domain notation like com.yourcompany.appname. It cannot be changed after submission, so choose carefully. Register it in the Apple Developer Portal before creating your app in App Store Connect.