EAS Build compiles your app on Expo's machines, which is how a Windows or Linux developer produces an iOS build at all, and how a team avoids "it builds on my laptop". It manages signing: for iOS it creates and stores the certificate and provisioning profile, for Android the upload keystore. Three profiles cover the lifecycle - development for a build with the dev client, preview for an internal install, production for the stores.
EAS Update ships JavaScript and asset changes over the air, without a store review. This is genuinely useful for a copy fix or a crash on a Friday. Two limits: it cannot change native code, so a new native dependency still needs a store build; and both stores forbid using it to change what the app substantially is. Bug fixes and content, yes. A new feature set you did not submit, no.
The submission itself is eas submit, which uploads to App Store Connect or Google Play. What delays a release is rarely the build. It is the metadata: screenshots at the required sizes for every device class, a description, a privacy policy URL that resolves, and the data safety declarations both stores now require - Apple's privacy nutrition labels and Google's Data Safety form - which must match what your app actually collects.
Two rejections catch almost every new app. An account that can be created but not deleted - both stores require in-app deletion. And a permission string that does not say why.
# eas.json - three profiles for the three jobs.
{
"cli": { "version": ">= 12.0.0" },
"build": {
"development": {
"developmentClient": true,
"distribution": "internal"
},
"preview": {
"distribution": "internal",
"channel": "preview",
"ios": { "simulator": false }
},
"production": {
"channel": "production",
"autoIncrement": true
}
},
"submit": {
"production": {
"ios": { "appleId": "you@example.com", "ascAppId": "1234567890" },
"android": { "serviceAccountKeyPath": "./play-service-account.json" }
}
}
}
# Build in the cloud - no Xcode needed, and no Mac for the iOS build.
eas build --platform ios --profile production
eas build --platform android --profile production
# Ship both store binaries.
eas submit --platform ios --latest
eas submit --platform android --latest
# An over-the-air fix: JavaScript and assets only, no review, minutes not days.
eas update --branch production --message "Fix the crash on an empty basket"
# NOT over the air: a new native dependency. That needs a store build.
# npx expo install expo-camera -> eas build, then eas submit