eas.json

Learn the eas.json configuration.

eas.json structure

eas.json is the configuration file for EAS services. It has three main sections: "build" for build profiles, "submit" for store submission, "cli" for general settings. Each section holds named profiles.

Profiles split by environment: development, preview, production. Each profile can take different signing, channel and version settings. This file goes into version control; keys and passwords never go here, they come from environment variables.

cli and app version

The "cli" section tunes EAS tool behavior. For example version pins the eas-cli version; this way the team uses the same release. appVersionSource decides where the version number comes from.

In the "production" profile autoIncrement raises the version number by one on every build. This prevents the "version conflict" error when submitting to the store. You write the setting as { "autoIncrement": true }. This way you do not bump the number by hand before each submit.

Exercise Write the production profile

Add a "production" profile to the "build" section of eas.json. The profile is an object carrying an "autoIncrement" field set to true.

Show example solution

{
  "build": {
    "preview": { "android": { "buildType": "apk" } },
    "production": {
      "autoIncrement": true
    }
  }
}

Test yourself

Write the development profile

"development": ____ { "developmentClient": true }

Show answer

"development": {} { "developmentClient": true }

What does autoIncrement do?
```
"production": { "autoIncrement": true }
```
- Raises the version number
- Shrinks the bundle size
- Cancels the build
- Changes the app icon
Show answer

Raises the version number — autoIncrement raises the version number by one on each build.
Match each section to its role

build

Build profiles
submit

Store submission
cli

Tool settings
production

Release environment

Next lesson: GitHub Actions

We Are Enhancing Your Experience

Cookie Preferences

Strictly Necessary Cookies

Analytical Cookies