HomeGuidesReferenceLearn
ArchiveExpo SnackDiscord and ForumsNewsletter

eas.json

Learn about available properties for EAS Build and EAS Submit to configure and override their default behavior from within your project.


eas.json is the configuration file for EAS CLI and services. It is located at the root of a project next to the package.json. You can find the complete reference of all available schema properties for EAS Build and EAS Submit on this page.

EAS Build

The following properties are available in the schema for the build key in eas.json.

Example schema of multiple build profiles
eas.json
{
  "build": {
    "base": {
      "node": "12.13.0",
      "yarn": "1.22.5",
      "env": {
        "EXAMPLE_ENV": "example value"
      },
      "android": {
        "image": "default",
        "env": {
          "PLATFORM": "android"
        }
      },
      "ios": {
        "image": "latest",
        "env": {
          "PLATFORM": "ios"
        }
      }
    },
    "development": {
      "extends": "base",
      "developmentClient": true,
      "env": {
        "ENVIRONMENT": "development"
      },
      "android": {
        "distribution": "internal",
        "withoutCredentials": true
      },
      "ios": {
        "simulator": true
      }
    },
    "staging": {
      "extends": "base",
      "env": {
        "ENVIRONMENT": "staging"
      },
      "distribution": "internal",
      "android": {
        "buildType": "apk"
      }
    },
    "production": {
      "extends": "base",
      "env": {
        "ENVIRONMENT": "production"
      }
    }
  }
}

Common properties for native platforms

PropertyDescription

(boolean) - When set to true, EAS CLI won't require you to configure credentials when building the app. This comes in handy when using EAS Build custom builds. Defaults to false.

(string) - The name of the build profile that the current one should inherit values from. This value can't be specified per platform.

(enum: local, remote) - The source of credentials used to sign the application archive.

  • local - if you want to provide your own credentials.json.
  • remote - if you want to use the credentials managed by EAS (default option).

(string) - Deprecated: Name of the release channel for the Classic Updates service, which is only supported in SDK 49 and lower. If you do not specify a channel, your binary will pull releases from the default channel.

EAS Update uses the channel field, so you can remove releaseChannel after migrating to EAS Update.

(string) - The EAS Update channel where this build will look for updates. Learn more. Standalone builds will check for and download updates matching platform, native runtime, and channel.

This field has no effect when developmentClient is set to true, as development builds can run updates from any channnel.

If you have not yet migrated from Classic Updates to EAS Update, then continue to use the releaseChannel field instead.

(enum: store, internal) - The method of distributing your app.

  • internal - with this option you'll be able to share your build URLs with anyone, and they will be able to install the builds to their devices straight from the Expo website. When using internal, make sure the build produces a .apk or ipa file. Otherwise, the shareable URL will be not work. See internal distribution for more information.
  • store - produces builds for store uploads, your build URLs won't be shareable.

(boolean) - If set to true (defaults to false), this field will produce a development build. For the build to be successful, the project must have expo-dev-client installed and configured.

Note: this field is for setting the gradleCommand to :app:assembleDebug for Android and buildConfiguration to Debug for iOS . If these fields are provided for the same build profile, will take precedence over developmentClient.

(enum: default, medium, large) - The resource class that will be used to run this build. To see mapping for each platform, see Android-specific resource class field and iOS-specific resource class field.

The large resource class is not available on the free plan.

(string) - Optional override of the prebuild command used by EAS.

For example, you can specify prebuild --template example-template to use a custom template.

Note: --platform and --non-interactive will be added automatically by the build engine, so you do not need to specify them manually.

(string[]) - List of paths (or patterns) where EAS Build is going to look for the build artifacts. Use applicationArchivePath for specifying the path for uploading the application archive. Build artifacts are uploaded even if the build fails. EAS Build uses the fast-glob npm library for pattern matching.

(string) - Version of Node.js.

(string) - Version of Yarn.

(string) - Version of pnpm.

(string) - Deprecated: Version of expo-cli used to prebuild your app. It only affects managed projects on Expo SDK 45 and lower.

For newer SDKs, EAS Build will use the versioned Expo CLI. It is included with expo library. You can opt out of using the versioned Expo CLI by setting the EXPO_USE_LOCAL_CLI=0 environment variable in the build profile.

(object) - Environment variables that should be set during the build process. It should only be used for values that you would commit to your git repository and not for passwords or secrets.

(boolean) - Controls how EAS CLI bumps your application build version. Defaults to false.

When enabled, for Android, bumps expo.android.versionCode (for example, 3to 4). For iOS, bumps the last component of expo.ios.buildNumber (for example, 1.2.3.39 to 1.2.3.40).

(object) - Cache configuration. This feature is intended for caching values that require a lot of computation. For example, compilation results (both final binaries and any intermediate files). However, it doesn't work well for node_modules because the cache is not local to the machine, so the download speed is similar to downloading from the npm registry.

(boolean) - Disables caching. Defaults to false.

(string) - Cache key. You can invalidate the cache by changing this value.

(array) - List of the paths that will be saved after a successful build and restored at the beginning of the next one. Both absolute and relative paths are supported, where relative paths are resolved from the directory with eas.json.

(string) - Custom workflow file name that will be used to run this build. You can also specify this property on platform level for platform-specific workflows. Learn more.

Example: "config": "production.yml" will use workflow from .eas/build/production.yml.

Android-specific options

PropertyDescription

(boolean) - When set to true, EAS CLI won't require you to configure credentials when building the app. This comes in handy when you want to build debug binaries and the debug keystore is checked in to the repository. Defaults to false.

(string) - Image with build environment.

(enum: default, medium, large) - The Android-specific resource class that will be used to run this build. Defaults to medium.

For information on available build resources for each resource class, see Android build server configurations.

The large resource class is not available on the free plan.

(string) - Version of Android NDK.

(boolean | "version" | "versionCode") - Controls how EAS CLI bumps your application build version. Defaults to false.

Allowed values:

  • "version" - bumps the patch of expo.version (for example, 1.2.3 to 1.2.4).
  • "versionCode" (or true) - bumps expo.android.versionCode (for example, 3 to 4).
  • false - versions won't be bumped automatically (default).

Based on the value of cli.appVersionSource in eas.json, the values will be updated locally in your project or on EAS servers.

(enum: app-bundle, apk) - Type of the artifact you want to build. It controls which Gradle task will be used to build the project. It can be overridden by gradleCommand or developmentClient: true option.

  • app-bundle - :app:bundleRelease
  • apk - :app:assembleRelease

(string) - Gradle task that will be used to build your project. For example, :app:assembleDebug to build a debug binary. It's not recommended unless you need to run a task that buildType does not support, it takes priority over buildType and developmentClient.

(string) - Path (or pattern) where EAS Build is going to look for the application archive. EAS Build uses the fast-glob npm library for pattern matching. The default value is android/app/build/outputs/**/*.{apk,aab}.

(string) - Custom workflow file name that will be used to run this Android build. You can also specify this property on profile level for platform-agnostic workflows. Learn more.

Example: "config": "production-android.yml" will use workflow from .eas/build/production-android.yml.

iOS-specific options

PropertyDescription

(boolean) - When set to true, EAS CLI won't require you to configure credentials when building the app. This comes in handy when using EAS Build custom builds. Defaults to false

(boolean) - If set to true, creates build for iOS Simulator. Defaults to false.

(enum: universal, adhoc) - Provisioning method used for "distribution": "internal" when you have an Apple account with Apple Developer Enterprise Program membership. You can choose if you want to use adhoc or universal provisioning. The latter is recommended as it does not require you to register each individual device. If you don't provide this option and you still authenticate with an enterprise team, you'll be prompted which provisioning method to use.

(boolean | "version" | "buildNumber") - Controls how EAS CLI bumps your application build version. Defaults to false.

Allowed values:

  • "version" - bumps the patch of expo.version (for example, 1.2.3 to 1.2.4).
  • "buildNumber" (or true) - bumps the last component of expo.ios.buildNumber (for example, 1.2.3.39 to 1.2.3.40).
  • false - versions won't be bumped automatically (default)

Based on the value of cli.appVersionSource in eas.json, the values will be updated locally in your project or on EAS servers.

(string) - Image with build environment.

(enum: default, medium, large) - The iOS-specific resource class that will be used to run this build. Defaults to medium.

For information on available build resources for each resource class, see iOS build server configurations.

The large resource class is not available on the free plan.

(string) - Version of bundler.

(string) - Version of fastlane.

(string) - Version of CocoaPods.

(string) - Xcode project's scheme. If a project:

  • Has multiple schemes, you should set this value.
  • Has only one scheme, it will be detected automatically.
  • Have multiple schemes schemes and if this value is not set, EAS CLI will prompt you to select one of them.

(string) - Xcode project's Build Configuration.

  • For an Expo project, the value is "Release" or "Debug". Defaults to "Release".
  • For a bare React Native project, defaults to the value specified in the scheme.

It takes priority over developmentClient.

(string) - Path (or pattern) where EAS Build is going to look for the application archive. EAS Build uses the fast-glob npm package for pattern matching. You should modify that path only if you are using a custom Gymfile. The default is ios/build/Build/Products/*-iphonesimulator/*.app when building for simulator and ios/build/*.ipa in other cases.

(string) - Custom workflow file name that will be used to run this iOS build. You can also specify this property on profile level for platform-agnostic workflows. Learn more.

Example: "config": "production-ios.yml" will use workflow from .eas/build/production-ios.yml.

EAS Submit

The following properties are available in the schema for the submit key in eas.json.

Example schema of with production profile
eas.json
{
  "cli": {
    "version": ">= 0.34.0"
  },
  "submit": {
    "production": {
      "android": {
        "serviceAccountKeyPath": "../path/to/api-xxx-yyy-zzz.json",
        "track": "internal"
      },
      "ios": {
        "appleId": "john@turtle.com",
        "ascAppId": "1234567890",
        "appleTeamId": "AB12XYZ34S"
      }
    }
  }
}

Android-specific options

PropertyDescription

(string) - Path to the JSON file with Google Service Account Key used to authenticate with Google Play.

(enum: production, beta, alpha, internal) - The track of the application to use.

(enum: completed, draft, halted, inProgress) - The status of a release.

(number) - The initial fraction of users who are eligible to receive the release. Should be a value from 0 (no users) to 1 (all users). Works only with inProgress release status.

(boolean) - Indicates that the changes sent with this submission will not be reviewed until they are explicitly sent for review from the Google Play Console UI. Defaults to false.

(string) - The application ID that is used when accessing Service Account Key managed by Expo. It does not have any effect if you are using local credentials. In most cases this value will be autodetected. However, if you have multiple product flavors, this value might be necessary.

iOS-specific options

PropertyDescription

(string) - Your Apple ID username (you can also set the EXPO_APPLE_ID env variable).

(string) - App Store Connect unique application Apple ID number. When set, results in skipping the app creation step.

(string) - Your Apple Developer Team ID.

(string) - An unique ID for your app that is not visible on the App Store, will be generated unless provided.

(string) - Primary language. Defaults to "en-US".

(string) - The name of your company, needed only for the first submission of any app to the App Store.

(string) - The name of your app as it will appear on the App Store. Defaults to expo.name from the app config.

(string) - The path to your App Store Connect Api Key .p8 file.

(string) - The Issuer ID of your App Store Connect Api Key.

(string) - The Key ID of your App Store Connect Api Key.

(string) - The bundle identifier that will be used when accessing submit credentials managed by Expo. It does not have any effect if you are using local credentials. In most cases, this value will be autodetected. However, if you have multiple Xcode schemes and targets, this value might be necessary.

(string) - The path to your store configuration file.