Build configuration process
In this guide you will learn what happens when EAS CLI configures your project with eas build:configure
(or eas build
- which runs this same process if the project is not yet configured).
EAS CLI performs the following steps when configuring your project:
If you only want to use EAS Build for a single platform, that's fine. If you change your mind, you can come back and the other later.
The command will create an eas.json
file in the root directory with the following contents:
{
"builds": {
"android": {
"release": {
"workflow": "generic"
}
},
"ios": {
"release": {
"workflow": "generic"
}
}
}
}
This is your EAS Build configuration. It defines a single build profile named
release
(you can have multiple build profiles like
release
,
debug
,
testing
, etc.) for each platform. In the generated configuration, each profile declares that the project is a generic React Native project (unlike a managed Expo project which doesn't contain native code in the project tree). If you want to learn more about
eas.json
see the
Configuration with eas.json page.
EAS CLI performs two steps:
Similar configuration step is performed for the iOS project. EAS Build resolved the bundle identifier and updates the project.pbxproj
file.
Make sure to choose the bundle identifier defined in app.json because it'll be used to identify you app on the Apple App Store.
That's all there is to configuring a project to be compatible with EAS Build.