EAS Submit

Automating App Store Connect and Play Console uploads - the cookbook for shipping EAS Build artifacts to TestFlight, App Review, and Google Play tracks on Expo SDK 57.

Recipe

Quick-reference recipe card - copy-paste ready.

# Build then submit latest artifact
eas build --profile production --platform ios
eas submit --platform ios --latest
 
eas build --profile production --platform android
eas submit --platform android --latest
 
# One-shot build + submit
eas build --profile production --platform ios --auto-submit

// eas.json
{
  "submit": {
    "production": {
      "ios": {
        "appleId": "release@example.com",
        "ascAppId": "1234567890",
        "appleTeamId": "ABCDE12345"
      },
      "android": {
        "serviceAccountKeyPath": "./secrets/play-service-account.json",
        "track": "internal"
      }
    }
  }
}

# Non-interactive CI submit
eas submit --platform all --profile production --latest --non-interactive

When to reach for this:

• QA passed on a preview build - promote the production artifact to stores.
• CI should upload to TestFlight / Play internal track on every main merge.
• Replacing manual Transporter.app or Play Console drag-and-drop uploads.
• Standardizing which Play track receives each profile's AAB.

Working Example

iOS - App Store Connect

Step 1 - Create App Store Connect API key

1. App Store Connect → Users and Access → Integrations → App Store Connect API.
2. Generate key with App Manager or Admin role.
3. Download .p8 once - store in team secrets vault.

eas credentials --platform ios
# Configure App Store Connect API key for submit

Step 2 - Configure eas.json

{
  "submit": {
    "production": {
      "ios": {
        "ascAppId": "1234567890",
        "appleTeamId": "ABCDE12345"
      }
    }
  }
}

Find ascAppId in App Store Connect → App Information → Apple ID (numeric).

Step 3 - Build and submit

eas build --profile production --platform ios
eas submit --platform ios --profile production --latest

Or with auto-submit:

{
  "build": {
    "production": {
      "distribution": "store",
      "autoIncrement": true
    }
  }
}

eas build --profile production --platform ios --auto-submit

• Submitted builds appear in TestFlight within minutes - TestFlight Distribution
• App Review submission is a separate step in App Store Connect after TestFlight validation
• Signing credentials come from iOS Credentials & Provisioning - submit uses different API keys

Android - Google Play Console

Step 1 - Create service account

1. Google Cloud Console → create service account with no default roles.
2. Play Console → Users and permissions → invite service account email.
3. Grant Release to production, exclude devices, and use Play App Signing (or narrower release permissions for CI).
4. Download JSON key → ./secrets/play-service-account.json (gitignored).

Step 2 - Configure eas.json tracks

{
  "submit": {
    "production": {
      "android": {
        "serviceAccountKeyPath": "./secrets/play-service-account.json",
        "track": "internal",
        "releaseStatus": "completed"
      }
    },
    "closed-beta": {
      "android": {
        "serviceAccountKeyPath": "./secrets/play-service-account.json",
        "track": "alpha"
      }
    }
  }
}

Step 3 - Build AAB and submit

eas build --profile production --platform android
eas submit --platform android --profile production --latest

• track": "internal" - fastest QA loop - Internal Testing Tracks
• Promote internal → closed → open → production in Play Console UI
• versionCode must exceed all prior uploads - use autoIncrement on build profile

Submit Profiles and CI

# .github/workflows/release.yml (excerpt)
name: Release
on:
  push:
    tags: ["v*"]
jobs:
  submit:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with: { node-version: 22 }
      - run: npm install -g eas-cli
      - run: eas submit --platform all --profile production --latest --non-interactive
        env:
          EXPO_TOKEN: ${{ secrets.EXPO_TOKEN }}

# Submit a specific build ID (not just --latest)
eas submit --platform ios --id <build-uuid>

• EXPO_TOKEN - machine token from expo.dev → Access tokens
• Store Apple .p8 and Play JSON as CI secrets - reference paths in eas.json or env overrides
• Gate submit on fingerprint unchanged or explicit release approval

Local Artifact Submit

Submit IPAs or AABs built outside EAS:

eas submit --platform ios --path ./dist/ShopApp.ipa
eas submit --platform android --path ./dist/ShopApp.aab --profile production

Use when:

• Migrating from legacy CI that produces artifacts locally
• Re-submitting a known-good build after a metadata-only rejection

Common Errors

FAQs

Related

• EAS Build Basics - producing store-shaped artifacts
• iOS Credentials & Provisioning - signing vs submit API keys
• Android Keystores & Signing - upload key alignment
• Internal Distribution - TestFlight and Play internal paths
• ../ios-platform/testflight-distribution/testflight-distribution.md - tester groups and build expiry
• ../ios-platform/app-store-review-guidelines/app-store-review-guidelines.md - review readiness
• ../android-platform/internal-testing-tracks/internal-testing-tracks.md - track promotion workflow
• ../cng-prebuild/cng-in-ci/cng-in-ci.md - CI build + submit pipelines
• ../expo-rules/release-and-ota-rules/release-and-ota-rules.md - OTA after store submit

Stack versions: This page was written for React 19.2.3, React Native 0.86.0, and Expo SDK 57 (expo ~57.0.4).