Learn how to create a production build for your app that is ready to be submitted to app stores from the command line using EAS Build.
EAS Build allows you to build a native app binary that is signed for app store submission. These types of builds are called production builds.
Production builds are submitted to app stores for release to the general public or as part of a store-facilitated testing process such as TestFlight.
These builds must be installed through their respective app stores. They cannot be installed directly on your Android Emulator or device, or iOS Simulator or device. The only exception to this is if you explicitly set "buildType": "apk"
for Android on your build profile. However, it is recommended to use aab when submitting to stores, and this is the default configuration.
eas.json
configurationA minimal configuration for building a production build in eas.json that is already created when you create your first build:
{
"build": {
%%placeholder-start%%... %%placeholder-end%%
"production": {}
%%placeholder-start%%... %%placeholder-end%%
}
}
To create a production build, run the following command for a platform:
-
eas build --platform android
-
eas build --platform ios
You can attach a message to the build by passing
--message
to the build command, for example,eas build --platform ios --message "Some message"
. The message will appear on the website. It comes in handy when you want to leave a note with the purpose of the build for your team.
Alternatively, you can use --platform all
option to build for Android and iOS at the same time:
-
eas build --platform all
You will need to have a developer account for the app store you want to submit your app.
You can build and sign your app using EAS Build, but you can't upload it to the Google Play Store unless you have a membership, a one-time $25 USD fee.
If you are going to use EAS Build to create release builds for the Apple App Store, you need access to an account with a $99 USD Apple Developer Program membership.
Before the build process can start for app stores, you will need to have a store developer account and generate or provide app signing credentials.
Whether you have experience with generating app signing credentials or not, EAS CLI does the heavy lifting. You can opt-in for EAS CLI to handle the app signing credentials process.
Generate new keystore
, and then you are done. The keystore is stored securely on EAS servers.By default, the eas build
command will wait for your build to complete, but you can interrupt it if you prefer not to wait. Monitor the progress and read the logs by following the link to the build details page that EAS CLI prompts once the build process gets started. You can also find this page by visiting your build dashboard or running the following command:
-
eas build:list
If you are a member of an organization and your build is on its behalf, you will find the build details on the build dashboard for that account.
Learn how to submit your app to app stores using EAS Submit.
Learn about the best practices for submitting your app to app stores.