Deploy

Quick Start

1. Install EAS CLI: npm install -g eas-cli
2. Login: npx eas login
3. Build iOS: eas build -p ios --profile production
4. Build Android: eas build -p android --profile production
5. Submit: eas submit -p ios or eas submit -p android

Process Workflow

Flow Diagram

┌─────────────────┐     ┌─────────────────┐     ┌─────────────────┐
│  Setup EAS      │────>│  Configure      │────>│  Build App      │
│  CLI & Login    │     │  Credentials    │     │  (Cloud/Local)  │
└─────────────────┘     └─────────────────┘     └─────────────────┘
                                                        │
                                                        v
┌─────────────────┐     ┌─────────────────┐     ┌─────────────────┐
│  Release to     │<────│  Store Review   │<────│  Submit to      │
│  Users          │     │  Process        │     │  App Store      │
└─────────────────┘     └─────────────────┘     └─────────────────┘

Phase Summary

Build Profiles

Build Caching

EAS Build includes automatic caching to speed up builds:

Cache Configuration

Each build profile includes cache configuration in eas.json:

{
  "cache": {
    "disabled": false,
    "key": "profile-v1",
    "cacheDefaultPaths": true,
    "customPaths": ["./ios/Podfile.lock"]
  }
}

Cache Keys

Invalidating Cache

To force a fresh build (when cache causes issues):

# Bump the cache key version in eas.json
# e.g., "key": "dev-v1" -> "key": "dev-v2"

Or use the EAS dashboard to clear cache for a specific build.

Phase 1: Setup EAS

Install EAS CLI

npm install -g eas-cli

Login to EAS

npx eas login
npx eas whoami  # Verify logged in

Update EAS CLI

npm install -g eas-cli@latest

Phase 2: Prerequisites

iOS (App Store Connect)

Required:

• Apple Developer Program membership ($99/year)
• App created in App Store Connect
• App-specific password for CI (optional)

Android (Google Play Console)

Required:

• Google Play Developer account ($25 one-time)
• App created in Play Console
• Service account key for automated submissions

Phase 3: Building

Development Builds

For testing on devices with development features:

# iOS (device)
task eas-build-ios
# Or: eas build -p ios --profile development

# Android
task eas-build-android
# Or: eas build -p android --profile development

# iOS (simulator only)
eas build -p ios --profile development:simulator

Production Builds

For store submission:

# iOS
eas build -p ios --profile production

# Android
eas build -p android --profile production

Local Builds

Build on your machine instead of EAS cloud:

# iOS (requires macOS + Xcode)
task eas-build-ios-local

# Android
task eas-build-android-local

Phase 4: Store Submission

Automatic Submission

Submit immediately after build:

# iOS
eas build -p ios --profile production --auto-submit

# Android
eas build -p android --profile production --auto-submit

Manual Submission

Submit an existing build:

# List recent builds
eas build:list

# Submit specific build
eas submit -p ios --id <build-id>
eas submit -p android --id <build-id>

Version Management

Automatic Version Management

Version numbers are managed automatically by EAS:

// eas.json
{
  "cli": {
    "appVersionSource": "remote"
  },
  "build": {
    "production": {
      "autoIncrement": true
    }
  }
}

Manual Version Setting

eas build:version:set

Code Signing

iOS Code Signing

EAS manages iOS code signing automatically. On first build:

1. EAS prompts to create/select certificates
2. Credentials are stored securely in EAS
3. Subsequent builds use stored credentials

To manage credentials:

eas credentials

Android Code Signing

EAS generates and manages the keystore. For Play Store:

1. First build creates a new keystore
2. Upload the app to Play Store
3. Subsequent builds use the same keystore

Environment Variables

EAS Secrets

Sensitive variables are stored in EAS Secrets (not in code):

1. Go to expo.dev > Project > Secrets
2. Add secrets for each environment:
   • GOOGLE_SERVICES_JSON - Firebase Android config (base64)
   • GOOGLE_SERVICE_INFO_PLIST - Firebase iOS config (base64)
   • SENTRY_AUTH_TOKEN - Sentry upload token

Environment-Specific Config

The ENVIRONMENT variable controls which config is used:

Over-the-Air Updates

For JavaScript-only updates (no native changes):

# Publish update to production channel
eas update --branch production --message "Bug fixes"

# Publish update to development channel
eas update --branch development --message "New feature"

Updates are automatically downloaded when users open the app.

When to Use OTA

Use OTA for:

• JavaScript/TypeScript bug fixes
• UI/UX changes
• Copy/text updates
• Logic changes

Requires full build for:

• Native module updates
• SDK version changes
• New native dependencies
• Permission changes

CI/CD Integration

GitHub Actions Example