Deploy

App Deployment SOP

Version: 1.0.0 Last Updated: 2026-01-11 Status: Active

Note: This is a template. Replace placeholders like {PROJECT_NAME}, {BUNDLE_ID}, and {BASE_URL} with your actual project values.

Overview

Purpose

Build and deploy the mobile app to the App Store and Google Play using EAS Build (Expo Application Services). This guide covers build profiles, code signing, store submission, version management, and over-the-air updates.

When to Use

ALWAYS: App store submissions, production builds, preview builds, OTA updates, version management SKIP: Local development builds, debugging, environment setup

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

name: Build and Deploy

on:
  push:
    branches: [main]

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3

      - uses: actions/setup-node@v3
        with:
          node-version: 18

      - name: Install dependencies
        run: npm install -g eas-cli && pnpm install

      - name: Build iOS
        run: eas build -p ios --profile production --non-interactive
        env:
          EXPO_TOKEN: ${{ secrets.EXPO_TOKEN }}

      - name: Build Android
        run: eas build -p android --profile production --non-interactive
        env:
          EXPO_TOKEN: ${{ secrets.EXPO_TOKEN }}

EXPO_TOKEN Setup

For CI/CD, create a robot token:

1. Go to expo.dev > Account Settings > Access Tokens
2. Create new token
3. Add as EXPO_TOKEN secret in your CI

Quick Reference

Common Commands

# Check build status
eas build:list

# View build details
eas build:view

# Cancel a build
eas build:cancel

# View submission status
eas submit:list

# Configure project
eas build:configure

# Update EAS CLI
npm install -g eas-cli@latest

# View credentials
eas credentials

# Publish OTA update
eas update --branch production --message "Description"

Build Commands

# Development iOS
eas build -p ios --profile development

# Development Android
eas build -p android --profile development

# Production iOS
eas build -p ios --profile production

# Production Android
eas build -p android --profile production

# iOS Simulator
eas build -p ios --profile development:simulator

# Local builds
task eas-build-ios-local
task eas-build-android-local

Submit Commands

# Submit iOS
eas submit -p ios

# Submit Android
eas submit -p android

# Auto-submit after build
eas build -p ios --profile production --auto-submit

Troubleshooting

Store Requirements Checklist

iOS App Store

• App icons (all sizes)
• Screenshots for required device sizes
• App description and keywords
• Privacy policy URL
• Support URL
• Age rating questionnaire
• App-specific content disclosures

Google Play Store

• App icons and feature graphic
• Screenshots for phone and tablet
• Short and full description
• Privacy policy URL
• Content rating questionnaire
• Target audience declaration
• Data safety form

Related Skills

Note: Skill paths (/skill-name) work after deployment. In the template repo, skills are in domain folders.

End of SOP