This documentation is available as Markdown for AI agents and LLMs. See the full Markdown index or append .md to any documentation URL.

Learn how to submit your iOS app to the Apple App Store with EAS Submit.

EAS Submit is the recommended way to upload your iOS app to the Apple App Store. The eas submit command works the same way on your machine and inside CI/CD. EAS Workflows is the simplest way to run it automatically after a build. EAS Submit works on macOS, Linux, and Windows, so you don't need a Mac to ship iOS builds.

Prerequisites

{
  "ios": {
    "bundleIdentifier": "com.yourcompany.yourapp"
  }
}

Build a production app

You need a production .ipa to submit. Create one with EAS Build:

Alternatively, build on your own computer with eas build --platform ios --profile production --local or with Xcode.

Submit with eas submit

Once the build is ready, submit it to the Apple App Store:

The command will walk you through selecting a build, prompt for your Apple ID on first run, and upload the binary to App Store Connect. The build appears in TestFlight after processing (usually 10-15 minutes). To release to production, log in to App Store Connect and submit the build for App Review.

Configure a submission profile

Add a submission profile in eas.json with your App Store Connect app ID:

{
  "submit": {
    "production": {
      "ios": {
        "ascAppId": "your-app-store-connect-app-id"
      }
    }
  }
}

How to find ascAppId

1. Sign in to App Store Connect and select your team.
2. Navigate to Apps.
3. Click your app.
4. Ensure the App Store tab is active.
5. On the left pane, under General, select App Information.
6. Your ascAppId is listed under General Information as Apple ID.

See the eas.json reference for every available option.

Build and submit in one step

Pass --auto-submit to eas build to hand the finished build off to EAS Submit automatically:

See Automate submissions for details.

Automate with EAS Workflows

EAS Workflows runs the same submit step on EAS infrastructure, triggered by a git push or run manually from the CLI. First, configure an App Store Connect API Key so workflows can authenticate with Apple non-interactively:

1. Select the production build profile.
2. Log in with your Apple Developer account and follow the prompts.
3. Select App Store Connect: Manage your API Key.
4. Select Set up your project to use an API Key for EAS Submit.

Create a workflow file named .eas/workflows/submit-ios.yml with the following contents:

name: Submit iOS

on:
  push:
    branches: ['main']

jobs:
  build_ios:
    name: Build iOS app
    type: build
    params:
      platform: ios
      profile: production

  submit_ios:
    name: Submit to TestFlight
    needs: [build_ios]
    type: testflight
    params:
      build_id: ${{ needs.build_ios.outputs.build_id }}

This builds an iOS app on every push to main and submits it to TestFlight. The pre-packaged testflight job can also share the build with internal and external testing groups. Trigger the workflow manually with:

See the workflow examples guide for more patterns.

Use other CI/CD services

You can run eas submit from any CI/CD service, such as GitHub Actions, GitLab CI, and others:

This requires a personal access token to authenticate with your Expo account. Set the EXPO_TOKEN environment variable in your CI service so eas submit can run non-interactively.

Manual fallback

If EAS Submit is temporarily unavailable, you can upload to the Apple App Store manually from a Mac with Xcode.