Skip to content
Tutorials Center
My learning

Topics

Lesson 28 of 38 ยท EAS Build and Updates

EAS Build and Build Profiles

Build Expo apps in the cloud with EAS Build: install the CLI, configure eas.json profiles for development, preview and production, extend profiles, auto-increment versions.

On your own machine, npx expo start runs your JavaScript inside Expo Go or a development build. To put a real app in front of testers or in an app store you need a binary: an .ipa file for iOS or an .apk/.aab file for Android. Making them normally needs a Mac with Xcode for iOS and the Android SDK for Android, plus careful handling of signing keys.

EAS Build (Expo Application Services) does this in the cloud. You run one command, Expo's servers build the app, and you download the result or send it straight to the stores. It also manages signing credentials for you.

What runs on this site. EAS needs your account and Expo's build servers, so the real commands and eas.json files are read-only. The runnable stand-in resolves profiles the way the CLI does (merging an extends chain), so you can see exactly which settings a build would use.

Install and log in

Terminal
npm install -g eas-cli      # or use: npx eas-cli <command>
eas login
eas init                    # links the project, writes the projectId into app config
eas build:configure         # creates eas.json

Understanding eas.json

eas.json holds named profiles. A profile is a recipe for one kind of build:

JSON
{
  "cli": { "version": ">= 16.0.0", "appVersionSource": "remote" },
  "build": {
    "development": {
      "developmentClient": true,
      "distribution": "internal",
      "ios": { "simulator": true },
      "android": { "buildType": "apk" }
    },
    "preview": {
      "distribution": "internal",
      "channel": "preview",
      "env": { "EXPO_PUBLIC_API_URL": "https://staging.example.com" }
    },
    "production": {
      "channel": "production",
      "autoIncrement": true,
      "env": { "EXPO_PUBLIC_API_URL": "https://api.example.com" }
    }
  },
  "submit": {
    "production": {}
  }
}

Build with eas build --platform ios --profile preview (or android, or all). With no --profile, EAS uses production.

The three classic profiles

Profile Purpose Key settings
development Daily coding. A custom Expo Go that includes your native libraries developmentClient: true, distribution: "internal"
preview Share with testers by link, close to the real app distribution: "internal", a channel
production The version going to the stores autoIncrement, store distribution (default)

Distribution has two values. store produces the file a store accepts (an .aab for Google Play, an App Store build for iOS). internal produces something you can install directly: an .apk on Android, or an ad hoc/enterprise-signed build on iOS that only registered devices can install (eas device:create registers an iPhone).

Development builds

Expo Go contains a fixed set of native modules. The moment you add a library with custom native code (a Bluetooth library, a different map SDK) or change native config, Expo Go cannot run it. A development build is your own Expo Go with your native modules and the dev tools:

Terminal
npx expo install expo-dev-client
eas build --profile development --platform android
npx expo start --dev-client

Build once, then iterate on JavaScript with fast refresh. Rebuild only when native dependencies or native config change.

flowchart LR
  A["Change JS only"] --> B["Fast refresh in dev build"]
  C["Add native library or edit plugins"] --> D["eas build --profile development"]
  D --> B
  B --> E["eas build --profile preview"]
  E --> F["eas build --profile production"]

Rebuild only when the native layer changes.

Reusing settings with extends

Profiles often share a lot. extends lets one profile start from another and override a few keys:

JSON
{
  "build": {
    "base": { "node": "22.12.0", "env": { "APP_VARIANT": "production" } },
    "preview":    { "extends": "base", "distribution": "internal", "env": { "APP_VARIANT": "preview" } },
    "production": { "extends": "base", "autoIncrement": true }
  }
}

Objects such as env are merged (child keys win), simple values are replaced.

Node.js Resolving profiles with extends (stand-in)

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with node:readline or process.stdin), it gets the next line from this box.

Versions: marketing and build numbers

Every store release has two numbers:

  • version (1.4.0): what users see. You set it in app config.
  • build number (iOS buildNumber) / version code (Android versionCode): an integer that must go up with every upload.

With "appVersionSource": "remote", EAS stores the build numbers on its servers, and "autoIncrement": true raises them for you on each production build. That removes the classic "this build number was already used" store error.

Node.js Auto-incrementing build numbers

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with node:readline or process.stdin), it gets the next line from this box.

Credentials

Signing proves that a build comes from you. iOS needs a distribution certificate and provisioning profile; Android needs a keystore. On first build eas build offers to generate and store them securely. Keep these facts in mind:

  • Never lose the Android upload key. EAS stores it for you; eas credentials lets you download a backup.
  • iOS builds need a paid Apple Developer account. Android needs a Google Play developer account only when you publish.
  • Credentials belong to the project on Expo's servers, so teammates can build without sharing files.

Useful commands and options

Terminal
eas build --platform all --profile production      # both stores
eas build --profile preview --local                # build on your own machine
eas build:list                                     # past builds
eas build --profile production --auto-submit       # build, then submit to stores
eas build:run --platform ios --latest              # install latest build on a simulator

Builds queue on a shared free tier and are faster on paid plans. A build fails visibly in the web logs at expo.dev, which is the first place to look. Typical causes: a library that needs native config not in your plugins, a wrong Node version (set node in the profile), or a missing environment variable.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is a development build?

    It is built from your project, so any native module you add works, and it connects to the Metro dev server.
  2. 2. What does distribution: internal produce?

    Internal distribution is for testers: install by link, without going through a store.
  3. 3. What does autoIncrement: true do with appVersionSource remote?

    Store uploads require a larger build number each time; EAS tracks and increments it.
  4. 4. When must you rebuild a development client?

    JavaScript changes reload instantly. Native changes need a new binary.

Summary

  • EAS Build compiles your iOS and Android binaries in the cloud and manages signing.
  • eas.json profiles describe each build kind; extends shares settings.
  • Use development builds for daily work, preview builds for testers, production builds for stores.
  • autoIncrement with remote version source avoids build-number clashes.
  • Rebuild natively only when native code or config changed.

Next: App config and environment variables