Next, this is what happens when EAS Build picks up your request:Ĭreate a new Docker container for the build. Upload the project tarball to a private AWS S3 bucket and send the build request to EAS Build. Actual behavior depends on the VCS workflow you are using. If the remote mode is selected but no credentials exist yet, you're prompted to generate a new keystore.Ĭreate a tarball containing a copy of the repository. Depending on the value of _NAME.credentialsSource, the credentials are obtained from either the local credentials.json file or from the EAS servers.Prepare the credentials needed for the build unless _NAME.withoutCredentials is set to true. If it's not clean, EAS CLI will provide an option to commit local changes for you or abort the build process. If cli.requireCommit is set to true in eas.json, check if the git index is clean - this means that there aren't any uncommitted changes. EAS CLI is in charge of completing the following steps: The first phase happens on your computer. We'll first run some steps on your local machine to prepare the project, and then we'll build the project on a remote service.
Let's take a closer look at the steps for building Android projects with EAS Build.
You may want to read this if you are interested in the implementation details of the build service. This page describes the process of building Android projects with EAS Build. Learn how an Android project is built on EAS Build.
0 kommentar(er)
