eas-app-stores

Run eas build -p ios --profile production --submit to build and submit in one step. You need an Apple Developer account, an app record in App Store Connect, and credentials configured via eas credentials or an App Store Connect API key.

Run npx testflight to build and submit to TestFlight with a single command. Set EXPO_APPLE_ID and EXPO_APPLE_TEAM_ID environment variables to skip interactive prompts on subsequent runs.

Create a service account in Google Cloud Console, link it in Play Console API access with release permissions, and add serviceAccountKeyPath to the android submit profile in eas.json. The app must already exist in Play Console before the first submission.

Yes. Set appVersionSource to remote and autoIncrement to true in eas.json, and EAS manages iOS build numbers and Android version codes automatically. You can inspect or override them with eas build:version:get and eas build:version:set.

Google Play rejects uploads when the versionCode was already used in a previous submission. Enable autoIncrement in your eas.json build profile or manually increment versionCode in app.json before rebuilding.

Yes, EAS Metadata uses a store.config.json file to manage titles, subtitles, keywords, descriptions, age ratings, and release settings. Run eas metadata:pull to fetch existing metadata and eas metadata:push to publish updates.