In our previous blog post, we explored how to build applications using the EAS Build service. This process generates artifacts (.aab for Android and .ipa for iOS), which must be uploaded to the app stores for user distribution.
Manually uploading these artifacts, or using internal tools like Transporter on MacOS, can be tedious, error-prone, and time-consuming. It's imperative to automate this process for efficiency.
This is solved with EAS Submit, a cloud-based solution that automatically uploads your build artifacts. It integrates seamlessly with other EAS products, offering a streamlined workflow.
To enable programmatic artifact uploads to the app stores, API access keys and service accounts are necessary for authorization.
We’ll guide you through generating all the required keys/accounts, downloading them, and uploading them to the EAS dashboard for future submissions.
For Android, follow these steps to create a Google Service Account with the necessary permissions.
After obtaining the .json file, upload it to the EAS dashboard under Project Settings -> Credentials -> Android -> Google Service Account Key.
Due to Google Play Store API limitations, a manual upload of the initial Android build file (.aab) is required. You can simply use the Google Play Store’s drag-and-drop interface for this.
For iOS submissions, follow these steps to create an App Store Connect API key.
Upon obtaining this .json file, upload it to the EAS dashboard under Project Settings -> Credentials -> iOS -> App Store Connect API Key.
Running the commands
After building with
eas build, submit the build artifact using
Typically, building and uploading to app stores are two separate steps. However, you can merge them into one with the
--auto-submit flag in the EAS build command.
This automation greatly simplifies the process. The command is as follows:
eas build --auto-submit
For more complex setups, such as different apps for each profile, customize the submission part with various profiles, similar to the EAS Build customization.
Uploading your app store credentials to the EAS dashboard ensures their automatic usage during submission.
Yet, you can tailor EAS Submit further via changes in the
eas.json file, like customizing the submit profile or using local credentials. The comprehensive list of options is detailed here.
Building and submitting locally
As mentioned in the previous post, it's possible to execute EAS commands locally. If you have a local build artifact, the same EAS command can be used to submit it to the app stores.
Automating submissions: Expo Documentation
EAS submit build command: GitHub - Expo EAS CLI