This documentation is available as Markdown for AI agents and LLMs. See the full Markdown index or append .md to any documentation URL.

Configuration with eas.json

Edit page

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


eas.json is the configuration file for EAS CLI and services. You can find a reference of all available schema properties for EAS CLI, Expo Build, and Expo Submit on this page.

EAS CLI

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

Properties

PropertyDescription

version

(string) - A semantic version range of EAS CLI versions that the project supports, such as >= 16.0.0. If the installed EAS CLI version is outside this range, EAS CLI stops with an error. The check is skipped when EAS_SKIP_CLI_VERSION_CHECK is set.

requireCommit

(boolean) - If true, eas build and eas update require a clean Git working tree. If EAS CLI finds uncommitted changes, it asks whether to commit them. In non-interactive mode, it stops instead. For a build, EAS CLI then uploads a shallow Git clone of your last commit. For more information, see Full Git workflow. Defaults to false.

appVersionSource

(enum: local, remote) - The source of your app's developer-facing build version (android.versionCode and ios.buildNumber). With remote, Expo servers store and manage the version. With local, Expo Build reads the version from your project files. If you omit this field, EAS CLI warns that it will be required in the future and uses local. When a build profile sets autoIncrement to true, EAS CLI asks you to choose a source and saves it to eas.json. For more information, see App version management.

promptToConfigurePushNotifications

(boolean) - If false, EAS CLI does not ask whether to set up push notification credentials when it sets up iOS credentials for a build. If you omit this field, EAS CLI asks only when the dependencies in your package.json include expo-notifications.

Expo 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": "22.23.3", "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

withoutCredentials

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

extends

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

credentialsSource

(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 Expo Services (default option).

releaseChannel

(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.

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

channel

(string) - The Expo 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 channel.

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

distribution

(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.

developmentClient

(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.

resourceClass

(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.

prebuildCommand

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

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.

buildArtifactPaths

(string[]) - List of paths (or patterns) where Expo 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. Expo Build uses glob patterns for pattern matching.

uploadSourceMaps

(boolean) - If set to true, the JavaScript source map generated during the build is uploaded to Expo servers. Stored source maps are used by Expo Observe to symbolicate reported error stack traces. The source code embedded in the map is removed before upload. Defaults to false.

Note: only available for builds that run on Expo Build servers. Local builds do not upload source maps.

node

(string) - Version of Node.js used for build.

corepack

(boolean) - If set to true, corepack will be enabled at the beginning of build process. Defaults to false.

yarn

(string) - Version of Yarn used for build.

pnpm

(string) - Version of pnpm used for build.

bun

(string) - Version of Bun used for build. You can also use a specific version. Learn how to configure the exact version in eas.json.

expoCli

(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, Expo 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.

env

(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.

autoIncrement

(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).

cache

(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.

disabled

(boolean) - Disables caching. Defaults to false.

key

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

paths

(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.

config

(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.

permissions

(object) - The role that the build acts with on the account. The role limits what the build's EXPO_TOKEN can do. If the role is lower than Release Manager and the build's environment has protected environment variables, the build fails. The person or robot that starts the build must have this role or a higher one in the role hierarchy, or the build fails. Without this field, the build acts with the role of the person or robot that starts it, up to Release Manager. When a build triggered from GitHub submits the app automatically, the submission also uses this role. In an Expo Workflows build job, the job's permissions take precedence. Requires EAS CLI 26.0.0 or later. Older versions report eas.json as invalid.

account

(object) - Permissions on the account that owns the project.

role

(enum: runner, developer, release_manager) - The role that the build acts with.

environment

(enum: development, preview, production) - The environment used to apply environment variables for the build process. Learn more.

Android-specific options

PropertyDescription

withoutCredentials

(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.

image

(string) - Image with build environment.

resourceClass

(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.

ndk

(string) - Version of Android NDK.

autoIncrement

(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 Expo servers.

buildType

(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 (creates .aab artifact)
  • apk - :app:assembleRelease (creates .apk artifact)

gradleCommand

(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.

applicationArchivePath

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

config

(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

withoutCredentials

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

simulator

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

enterpriseProvisioning

(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.

autoIncrement

(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 Expo servers.

image

(string) - Image with build environment.

resourceClass

(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.

bundler

(string) - Version of bundler.

fastlane

(string) - Version of fastlane.

cocoapods

(string) - Version of CocoaPods.

scheme

(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 and if this value is not set, EAS CLI will prompt you to select one of them.

buildConfiguration

(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.

applicationArchivePath

(string) - Path (or pattern) where Expo Build is going to look for the application archive. Expo Build uses glob patterns 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.

config

(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.

Expo 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": { "track": "internal" }, "ios": { "appleId": "john@turtle.com", "ascAppId": "1234567890", "appleTeamId": "AB12XYZ34S" } } } }

Android-specific options

PropertyDescription

serviceAccountKeyPath

(string) - Path to the JSON file with Google Service Account Key used to authenticate with Google Play. The path can include environment variables, such as $GOOGLE_SERVICE_ACCOUNT_KEY_PATH, which EAS CLI replaces with values from the environment where it runs. If you omit this field, Expo Submit uses the key that is assigned to your app on Expo servers.

track

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

releaseStatus

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

rollout

(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.

changesNotSentForReview

(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.

applicationId

(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

appleId

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

ascAppId

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

appleTeamId

(string) - Your Apple Developer Team ID.

sku

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

language

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

companyName

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

appName

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

ascApiKeyPath

(string) - The path to your App Store Connect API Key .p8 file. The path can include environment variables, such as $ASC_API_KEY_PATH, which EAS CLI replaces with values from the environment where it runs.

ascApiKeyIssuerId

(string) - The Issuer ID of your App Store Connect API Key. The value can include environment variables, such as $ASC_API_KEY_ISSUER_ID, which EAS CLI replaces with values from the environment where it runs.

ascApiKeyId

(string) - The Key ID of your App Store Connect API Key. The value can include environment variables, such as $ASC_API_KEY_ID, which EAS CLI replaces with values from the environment where it runs.

bundleIdentifier

(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.

metadataPath

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

groups

(array) - An array of TestFlight internal group names to add the build to. Note: on top of the groups you provide here, the build will be automatically added to the groups that have been created with the "Enable automatic distribution" App Store Connect setting.

⌂ 换网址