Skip to main content
First-time vibe coding to App Store Level: Beginner 16 min read

iOS App Store Shipping Checklist: Prerequisites for AI-Generated Apps

A complete 16-point interactive shipping checklist for vibe coders and AI developers taking an iOS app from prototype to App Store release. Clearly distinguishes build tools, portal prerequisites, and FlightDeck MCP automation.

Published: 2026-11-01 • Last Updated: 2026-11-01 • Author: Kip Lawrence
Key MCP Tools: release_readiness_checkrelease_submission_diagnostics_getapps_list

Overview: The Complete Path from AI Code to the App Store

When you build an iOS app using an AI coding assistant (like Cursor, Claude Code, or Google Antigravity), generating the user interface and business logic is often the fastest phase. The real friction begins when moving the application into Apple's distribution pipeline: enrolling in the Developer Program, provisioning certificates, uploading signed binaries, configuring 39 localizations, declaring privacy nutrition labels, and clearing App Review.

To avoid costly rejections and delays, this guide provides a 16-point, sequential shipping checklist.

TEXT
┌───────────────────────────────────────────────────────────────┐
│ The Five Shipping Phases                                      │
├─────────────────┬─────────────────────────────────────────────┤
│ 1. Foundations  │ Apple Enrollment, Team API Key, App Record  │
│ 2. Binary Build │ Code Signing, Compilation, Build Versioning │
│ 3. TestFlight   │ IPA Ingestion, Internal/External Testing    │
│ 4. Storefront   │ Screenshots, Localized Metadata, Compliance │
│ 5. Submission   │ Pre-Flight Audit, App Review, Live Release  │
└─────────────────┴─────────────────────────────────────────────┘
Note

Who Handles What:

  • Your AI Coding Assistant: Writes code, fixes compiler errors, and writes release notes.
  • Xcode / Flutter CLI / Fastlane: Compiles native source code into an encrypted, signed .ipa archive.
  • Apple Web Portal: Legal agreements (Paid Apps Agreement), financial banking details, and initial App ID creation.
  • FlightDeck MCP: Automates binary validation, chunked uploads, TestFlight distribution, storefront metadata, screenshot management, readiness audits, and review submission staging.
  • Apple App Review: Evaluates your submitted binary against App Store Review Guidelines.

The 16-Point Shipping Checklist

Work through each step in sequence before submitting your application to Apple:

[ ] Step 1: Enroll in the Apple Developer Program

[ ] Step 2: Accept Agreements and Banking (Conditional on Monetization)

  • Responsible Tool: App Store Connect Web Portal (Agreements, Tax, and Banking).
  • Requirement: Conditional: If your app sells subscriptions, in-app purchases, or upfront paid downloads, the Account Holder must sign the Paid Applications Agreement and provide banking and tax details (W-8BEN / W-9). Free apps without monetization do NOT require the Paid Applications agreement or banking setup.

[ ] Step 3: Reserve Bundle ID and Create App Record

  • Responsible Tool: Apple Developer Portal & App Store Connect Web Portal.
  • Requirement: In Certificates, Identifiers & Profiles, register an explicit App ID (e.g., com.yourcompany.yourapp). In App Store Connect (My Apps > +), create the app record with your primary language, app name, and SKU.
  • Guide: How to Create an App Record and Reserve Your Name.

[ ] Step 4: Generate App Store Connect API Key

  • Responsible Tool: App Store Connect Web Portal (Users and Access > Integrations).
  • Requirement: Generate a Team API Key with Admin or App Manager role. Download the .p8 private key file (Apple permits downloading this exactly once). Import it into FlightDeck Desktop under Settings > Connection Profiles.
  • Guide: App Store Connect API Keys Guide: Generating Team Keys for AI Agents.

Phase 2: Local Compilation and Signing

[ ] Step 5: Configure Semantic Versioning and Monotonic Build Numbers

  • Responsible Tool: Xcode project settings / Info.plist.
  • Requirement:
  • CFBundleShortVersionString (Version): Visible version string (e.g., 1.0.0).
  • CFBundleVersion (Build): Internal integer or dotted integer that must strictly increment with every upload (e.g., 1, 2, 3). Reusing a build number causes rejection ITMS-90189.
  • Guide: App Store Version vs Build Numbering Rules for Automated Pipelines.

[ ] Step 6: Compile and Sign the Production .ipa Archive

  • Responsible Tool: xcodebuild, Flutter CLI (flutter build ipa), or Fastlane.
  • Requirement: FlightDeck does not compile code or sign binaries; it accepts compiled archives. Build your app using an Apple Distribution signing certificate and App Store provisioning profile.
  • Guides: Flutter: Build IPA to App Store Connect • React Native / Expo IPA Upload.

Phase 3: Binary Ingestion and TestFlight Testing

[ ] Step 7: Pre-Upload Binary Validation

  • Responsible Tool: FlightDeck MCP (build_upload_preview).
  • Prompt: ``text Using FlightDeck, inspect our compiled binary at ./build/App.ipa. Validate its bundle identifier, version string, build number, and entitlements before we start uploading. ``
  • Guide: Pre-Upload Binary Validation Checks for iOS IPAs.

[ ] Step 8: Upload Binary and Monitor Ingestion

  • Responsible Tool: FlightDeck MCP (build_upload_start, builds_list).
  • Prompt: ``text Using FlightDeck, upload our validated IPA to App Store Connect and monitor its ingestion processing status until it is ready for testing. ``

[ ] Step 9: Validate with Internal TestFlight Testers

  • Responsible Tool: FlightDeck MCP (beta_groups_list, build_add_to_beta_group).
  • Requirement: Add the newly processed build to an internal testing group (up to 100 team members). Internal TestFlight does not require Beta App Review. However, the build must first finish Apple's automated ingestion processing (transcoding and binary checks) and satisfy export compliance before it becomes available to internal testers.
  • Guide: Automating TestFlight Beta Distribution with an AI Agent.

Phase 4: Storefront Assets and Regulatory Disclosures

[ ] Step 10: Configure Required Storefront Screenshots

[ ] Step 11: Provide Storefront Metadata, Keywords, and URLs

  • Responsible Tool: FlightDeck MCP (app_store_version_localization_update).
  • Requirement:
  • App Name: Max 30 characters.
  • Subtitle: Max 30 characters.
  • Keywords: Max 100 characters (comma-separated, no spaces after commas).
  • Privacy Policy URL: Publicly reachable HTTPS URL (mandatory for all apps).
  • Support URL: Publicly reachable customer contact page.
  • Guide: App Store Metadata Character Limits: Rules for Names, Subtitles, and Keywords.

[ ] Step 12: Complete App Privacy Nutrition Labels

[ ] Step 13: Export Compliance (Encryption Attestation)

  • Responsible Tool: Info.plist or FlightDeck staged operation (flightdeck_operation_stage).
  • Requirement: Include ITSAppUsesNonExemptEncryption = false in your app's Info.plist if using standard HTTPS/TLS encryption. If omitted, builds stall in processing awaiting compliance signoff.
  • Guide: Fixing Missing Encryption Key ITSAppUsesNonExemptEncryption.

[ ] Step 14: Reviewer Notes and Demo Account Credentials

  • Responsible Tool: App Store Connect Web Portal / FlightDeck MCP.
  • Requirement: If your app requires a user login to access features, provide an active, unrestricted test account and password in App Review Information. Missing demo credentials cause immediate rejection under Guideline 2.1 (App Completeness).
  • Guide: Writing Effective App Review Notes: Demo Accounts and Reviewer Guidance.

Phase 5: Submission and Release

[ ] Step 15: Run Pre-Flight Release Readiness Check

  • Responsible Tool: FlightDeck MCP (release_readiness_check).
  • Prompt: ``text Using FlightDeck, run a pre-flight release readiness audit on our draft version for [App Name]. Report any missing screenshots, unattached builds, missing support URLs, or metadata compliance blockers before we submit. ``
  • Guide: Pre-Flight App Store Submission Readiness Check.

[ ] Step 16: Stage and Sign Off on App Review Submission

  • Responsible Tool: FlightDeck MCP (review_submission_create_draft, review_submission_submit).
  • Prompt: ``text Using FlightDeck, create an App Review submission draft for [App Name], attach build 42 to version 1.0.0, and stage the review submission. Do not submit to Apple without my explicit signoff in the Approval Center. ``
  • Approval Action: Open FlightDeck Desktop, inspect the visual submission card in the Approval Center, and click Approve Mutation. FlightDeck submits your release directly to Apple.

Connect Your AI Agent to App Store Connect

FlightDeck runs locally on your Mac, keeping private keys secure in your macOS Keychain and executing mutations only after your explicit approval.

Download FlightDeck on Mac App Store