EAS Submit
Also called Store submission
- Part of
- React Native Glossary
- Updated
What is EAS Submit in React Native?
EAS Submit is Expo’s service for uploading a finished React Native binary to App Store Connect or Google Play from the command line or CI, without opening Xcode.
EAS Submit is the part of EAS that takes a built .ipa or .aab and uploads it to the stores. It replaces dragging a file into Transporter or clicking through the Play Console upload form, and works with binaries from EAS Build or ones you built yourself.
eas submit --platform ios --latest
eas build --platform all --profile production --auto-submitIt authenticates differently on each store:
- iOS uses an App Store Connect API key, which EAS can generate and store for you. The binary lands in App Store Connect, processes, and appears in TestFlight.
- Android uses a Google Cloud service account JSON key with access to your Play developer account. A
submitprofile ineas.jsonchooses the track (internal,alpha,beta,production) and release status.
Two misconceptions are worth clearing up. First, “submit” means upload, not review: on iOS you still pick the build, fill in release notes and press Submit for Review in App Store Connect, and on Android a draft release still has to be rolled out. Second, the very first Android upload for a new app cannot go through the API. Google requires one manual upload in the Play Console before any automated tool, EAS Submit included, can push to that package name.
Most teams end up chaining build and submit, either with --auto-submit or as two jobs in a pipeline, so a merge to main ends with a binary waiting in TestFlight and the Play internal testing track. See the EAS Submit docs.