EAS setup

The mobile app already includes apps/mobile/eas.json, expo-updates, a runtime version policy, and Nx wrappers for common EAS commands. Replace all starter account and store identifiers before building your app.

Link your Expo project

Install and authenticate the EAS CLI, then initialize from the mobile app directory:

npm install --global eas-cli
eas login
cd apps/mobile
eas init

Confirm that apps/mobile/app.json contains your Expo owner, extra.eas.projectId, and the matching updates.url. Do not retain the starter’s project ID or owner. app.config.js applies identity suffixes from EXPO_PUBLIC_APP_ENV. Verify the evaluated config before allowing EAS to create credentials:

EXPO_PUBLIC_APP_ENV=production npx expo config --type public

Included profiles

apps/mobile/eas.json maps every build profile to an EAS environment and update channel:

Profile	Distribution	EAS environment	Channel	Purpose
`dev`	internal	`development`	`dev`	Installable development-environment build
`dev-store`	store	`development`	`dev`	Store-signed development variant
`preview`	internal	`preview`	`preview`	Installable preview build
`preview-store`	store	`preview`	`preview`	Store-signed preview variant
`production`	internal	`production`	`production`	Internal production-environment build
`production-store`	store	`production`	`production`	Store release build

All profiles auto-increment the remote app version. The CLI uses remote versioning. None of the current profiles enables a development client; dev is an environment name, not an Expo development-client build.

The root build:production command uses the internal production profile. Use production-store directly when you need a store-distribution artifact.

Configure EAS environments

Create client values separately for development, preview, and production:

cd apps/mobile

eas env:set \
  --environment production \
  --name EXPO_PUBLIC_APP_ENV \
  --value production \
  --visibility plaintext

eas env:set \
  --environment production \
  --name EXPO_PUBLIC_API_URL \
  --value https://api.example.com \
  --visibility plaintext

eas env:list --environment production

Repeat with development and preview, setting EXPO_PUBLIC_APP_ENV to the matching value. Pull an environment for local use with eas env:pull --environment development; delete a selected value with eas env:delete. EXPO_PUBLIC_* values are embedded public client configuration, even when EAS marks them sensitive. See Environment variables for the complete list and security model.

Build

Use the root wrappers for their matching internal profiles:

bun run build:dev
bun run build:preview
bun run build:production

Platform-specific wrappers exist for dev and preview:

bun run build:dev:ios
bun run build:dev:android
bun run build:preview:ios
bun run build:preview:android

Build a store profile directly from apps/mobile:

cd apps/mobile
eas build --profile production-store --platform all

The mobile package’s eas-build-post-install script returns to the repository root and runs tools/scripts/eas-build-post-install.mjs, which is required for this monorepo layout.

Credentials and submission

Let EAS inspect or create signing credentials:

cd apps/mobile
eas credentials

Before submission, replace every starter appleTeamId and ascAppId in eas.json. Configure the Android service account through EAS when prompted. The root submit scripts use the corresponding *-store submit profiles:

bun run submit:dev
bun run submit:preview
bun run submit:production

Each has :ios and :android variants. The current Android submit profiles target the internal Play track; development and preview submissions start as drafts. Review those settings before release.

Updates

Build profiles already declare dev, preview, and production channels. Publish with the EAS environment that matches the installed build:

cd apps/mobile
eas update --channel production --environment production --message "Release fixes"

The app uses runtimeVersion.policy: "appVersion". Native changes or an incompatible runtime require a new build rather than an update.

Inspect builds

cd apps/mobile
eas build:list
eas build:view BUILD_ID
eas project:info

AI tools

Release configuration

Link your Expo project

Included profiles

Configure EAS environments

Build

Credentials and submission

Updates

Inspect builds

Official documentation

Next steps

​Link your Expo project

​Included profiles

​Configure EAS environments

​Build

​Credentials and submission

​Updates

​Inspect builds

​Official documentation

​Next steps

Link your Expo project

Included profiles

Configure EAS environments

Build

Credentials and submission

Updates

Inspect builds

Official documentation

Next steps