EAS Submit

Expo · Reference cheat sheet

📋 Overview

eas submit uploads a build to App Store Connect or Google Play. Pair with eas build artifacts (local path or latest build on EAS). Configure credentials once; automate with CI profiles in eas.json.

🔧 Core concepts

Submit ≠ review: you still complete store listing / review in consoles.

💡 Examples

// eas.json (excerpt)
{
  "cli": { "version": ">= 12.0.0" },
  "build": {
    "production": { "channel": "production" }
  },
  "submit": {
    "production": {
      "ios": {
        "ascAppId": "1234567890"
      },
      "android": {
        "serviceAccountKeyPath": "./play-service-account.json",
        "track": "internal"
      }
    }
  }
}

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

eas build -p android --profile production
eas submit -p android --profile production --path ./app-release.aab

⚠️ Pitfalls

• Submitting a build with wrong version/build number.
• Committing Play/ASC private keys to git.
• Using production track before internal testing.
• Assuming submit publishes immediately—manual rollout/review may remain.

🔗 Related

• build.md — EAS Build
• keystore_sign.md — Android signing
• updates_ota.md — JS updates vs binaries
• commands.md — CLI
• config.md — version / bundle ids