Eas App Stores

Submitting to iOS App Store

For native SwiftUI/UIKit apps without a React Native runtime, configure the Xcode/EAS path in native-ios.md first. The signing, App Store Connect, and review stages below apply to both native Swift and Expo/React Native apps.

Contents

• Prerequisites

• Credential Setup

• Submission Commands

• App Store Connect Configuration

• TestFlight vs App Store

• Complete the Public Release

• App Review Process

• Version and Build Numbers

• Release Options

• Certificates and Provisioning

• App Store Metadata

• Troubleshooting

• CI/CD Integration

• Tips

Prerequisites

1. Apple Developer Account - Enroll at developer.apple.com

2. App Store Connect App - Create your app record before first submission

3. Apple Credentials - Configure via EAS or environment variables

Credential Setup

Using EAS Credentials

eas credentials -p ios

This interactive flow helps you:

• Create or select a distribution certificate

• Create or select a provisioning profile

• Configure App Store Connect API key (recommended)

App Store Connect API Key (Recommended)

API keys avoid 2FA prompts in CI/CD:

Use eas credentials -p ios to select the build profile and configure its App Store Connect API key. Reuse a working managed key when one already exists. For an existing local team API key, configure the submit profile explicitly:

Configure in eas.json:

{
  "submit": {
    "production": {
      "ios": {
        "ascApiKeyPath": "./AuthKey_XXXXX.p8",
        "ascApiKeyIssuerId": "xxxxx-xxxx-xxxx-xxxx-xxxxx",
        "ascApiKeyId": "XXXXXXXXXX"
      }
    }
  }
}

Keep private key material outside version control. Use the installed CLI's credential flow and current documentation when setting up a different key type.

Apple ID Authentication (Alternative)

For manual submissions, you can use Apple ID:

[email protected]
EXPO_APPLE_TEAM_ID=XXXXXXXXXX
EXPO_APPLE_APP_SPECIFIC_PASSWORD=xxxx-xxxx-xxxx-xxxx

The app-specific password is for the upload flow. Interactive Apple Developer signing setup has a separate authentication flow.

Submission Commands

# Build and submit to App Store Connect
eas build -p ios --profile production --auto-submit

# Submit the verified build
eas submit -p ios --profile production --id BUILD_ID

# Expo / React Native TestFlight shortcut
npx testflight

App Store Connect Configuration

First-Time Setup

Before submitting, complete in App Store Connect:

1. App Information

   • Primary language

   • Bundle ID (must match the archive; Xcode is authoritative for checked-in native projects)

   • SKU (unique identifier)

2. Pricing and Availability

   • Price tier

   • Available countries

3. App Privacy

   • Privacy policy URL

   • Data collection declarations

4. App Review Information

   • Contact information

   • Demo account (if login required)

   • Notes for reviewers

EAS Configuration

{
  "cli": {
    "version": ">= 16.0.1",
    "appVersionSource": "remote"
  },
  "build": {
    "production": {
      "ios": {
        "resourceClass": "m-medium",
        "autoIncrement": true
      }
    }
  },
  "submit": {
    "production": {
      "ios": {
        "appleId": "[email protected]",
        "ascAppId": "1234567890",
        "appleTeamId": "XXXXXXXXXX"
      }
    }
  }
}

Find ascAppId in App Store Connect → App Information → Apple ID.

TestFlight vs App Store

TestFlight (Beta Testing)

• Builds appear after Apple processing; compliance and group assignment may still need attention

• Internal testers (up to 100) - verify the build is available to the intended group

• External testers (up to 10,000) - requires beta review

• Builds expire after 90 days

App Store (Production)

• Requires passing App Review

• Submit for review from App Store Connect

• Choose release timing (immediate, scheduled, manual)

Complete the Public Release

EAS Submit uploads the binary to App Store Connect. Public distribution continues through the app version's App Review and release flow, as described in the EAS Submit guide.

1. Open the correct app and iOS version in App Store Connect. In its Build section, select the exact processed version/build you verified. Reuse an eligible TestFlight build when its code, icon, and configuration are ready for production; build again when those must change. Confirm the build is selectable for the App Store version. See Apple's build-selection guide.

2. Complete the required listing and review information: screenshots, description, support/privacy URLs, age rating, privacy declarations, export compliance, reviewer contact/login, and pricing/availability as applicable. Resolve the version's outstanding requirements before submission.

3. Choose the requested release timing: manual release, automatic release after approval, or automatic release no earlier than a chosen date. Approval is still required for the date-based option.

4. Click Add for Review, inspect the draft submission, then Submit for Review. Adding to a draft alone does not send it to Apple. Handle review messages and verify the resulting status. See Apple's submission steps.

5. After approval, follow the selected release timing. For manual release, the version waits in Pending Developer Release until Release This Version is completed. Verify availability in the intended storefronts before reporting it live. See Apple's release options.

Perform these publication steps only within the requested release scope. Preparing documentation or uploading a TestFlight beta does not itself request a public launch. Report the exact version/build and distinguish uploaded, submitted for review, approved, and publicly available.

App Review Process

What Reviewers Check

1. Functionality - App works as described

2. UI/UX - Follows Human Interface Guidelines

3. Content - Appropriate and accurate

4. Privacy - Data handling matches declarations

5. Legal - Complies with local laws

Common Rejection Reasons

Expedited Review

Request expedited review for:

• Critical bug fixes

• Time-sensitive events

• Security issues

Go to App Store Connect → your app → App Review → Request Expedited Review.

Version and Build Numbers

iOS uses two version identifiers:

• Version (CFBundleShortVersionString): User-facing, e.g., "1.2.3"

• Build Number (CFBundleVersion): Internal, must increment for each upload

For Expo projects whose native files are generated from app config, configure in app.json:

{
  "expo": {
    "version": "1.2.3",
    "ios": {
      "buildNumber": "1"
    }
  }
}

With autoIncrement: true and remote versioning, EAS increments its counter and writes native version metadata during the build. When setting up or changing native Swift versioning, or diagnosing a duplicate build number, verify the archive's CFBundleVersion as described in native-ios.md. A changing remote counter does not prove Xcode used it.

Release Options

These JSON examples are fragments of store.config.json for EAS Metadata. They configure release timing; uploading with EAS Submit still requires selecting the processed build and completing App Review before a public release.

Automatic Release

Release immediately when approved:

{
  "apple": {
    "release": {
      "automaticRelease": true
    }
  }
}

Scheduled Release

{
  "apple": {
    "release": {
      "automaticRelease": "2025-03-01T10:00:00Z"
    }
  }
}

Phased Release

Gradual rollout over 7 days:

{
  "apple": {
    "release": {
      "phasedRelease": true
    }
  }
}

Rollout: Day 1 (1%) → Day 2 (2%) → Day 3 (5%) → Day 4 (10%) → Day 5 (20%) → Day 6 (50%) → Day 7 (100%)

Certificates and Provisioning

Distribution Certificate

• Required for App Store submissions

• Limited to 3 per Apple Developer account

• Valid for 1 year

• EAS manages automatically

Provisioning Profile

• Links app, certificate, and entitlements

• App Store profiles don't include device UDIDs

• EAS creates and manages automatically

Check Current Credentials

eas credentials -p ios

App Store Metadata

Use EAS Metadata to manage App Store listing from code:

# Pull existing metadata
eas metadata:pull

# Push changes
eas metadata:push

See ./app-store-metadata.md for detailed configuration.

Troubleshooting

"No suitable application records found"

Create the app in App Store Connect first with matching bundle ID.

"The bundle version must be higher"

Compare the number inside the rejected archive with EAS's remote counter. For native Swift, check the plist/build-setting ownership described in native-ios.md, then rebuild and submit the corrected artifact.

"Missing compliance information"

Review the app's actual encryption use and complete Apple's export-compliance requirements. For an Expo app generated from app config, an exempt app can declare:

{
  "expo": {
    "ios": {
      "config": {
        "usesNonExemptEncryption": false
      }
    }
  }
}

For a checked-in Swift app, the equivalent declaration belongs in its native Info.plist as ITSAppUsesNonExemptEncryption. Use the value appropriate to the app; changing app.json alone does not update its native plist.

"Invalid provisioning profile"

eas credentials -p ios

Build stuck in "Processing"

App Store Connect processing can take 5-30 minutes. Check status in App Store Connect → TestFlight.

CI/CD Integration

For automated submissions in CI/CD:

# .eas/workflows/release.yml
name: Upload production iOS build

on:
  push:
    tags: ['v*']

jobs:
  build:
    type: build
    params:
      platform: ios
      profile: production

  submit:
    type: submit
    needs: [build]
    params:
      build_id: ${{ needs.build.outputs.build_id }}
      profile: production

Tips

• Submit to TestFlight early and often for feedback

• Use beta app review for external testers to catch issues before App Store review

• Respond to reviewer questions promptly in App Store Connect

• Keep demo account credentials up to date

• Monitor App Store Connect notifications for review updates

• Use phased release for major updates to catch issues early