home / skills / marcoodignoti / couple-diary / deployment

deployment skill

/.agent/skills/deployment

This skill helps you deploy Expo apps across iOS, Android, and web using EAS, automating builds, submissions, and hosting workflows.

npx playbooks add skill marcoodignoti/couple-diary --skill deployment

Review the files below or copy the command above to add this skill to your agents.

Files (6)
SKILL.md
3.6 KB
---
name: deployment
description: Deploying Expo apps to iOS App Store, Android Play Store, web hosting, and API routes
version: 1.0.0
license: MIT
---

# Deployment

This skill covers deploying Expo applications across all platforms using EAS (Expo Application Services).

## References

Consult these resources as needed:

- ./references/workflows.md -- CI/CD workflows for automated deployments and PR previews
- ./references/testflight.md -- Submitting iOS builds to TestFlight for beta testing
- ./references/app-store-metadata.md -- Managing App Store metadata and ASO optimization
- ./references/play-store.md -- Submitting Android builds to Google Play Store
- ./references/ios-app-store.md -- iOS App Store submission and review process

## Quick Start

### Install EAS CLI

```bash
npm install -g eas-cli
eas login
```

### Initialize EAS

```bash
npx eas-cli@latest init
```

This creates `eas.json` with build profiles.

## Build Commands

### Production Builds

```bash
# iOS App Store build
npx eas-cli@latest build -p ios --profile production

# Android Play Store build
npx eas-cli@latest build -p android --profile production

# Both platforms
npx eas-cli@latest build --profile production
```

### Submit to Stores

```bash
# iOS: Build and submit to App Store Connect
npx eas-cli@latest build -p ios --profile production --submit

# Android: Build and submit to Play Store
npx eas-cli@latest build -p android --profile production --submit

# Shortcut for iOS TestFlight
npx testflight
```

## Web Deployment

Deploy web apps using EAS Hosting:

```bash
# Deploy to production
npx expo export -p web
npx eas-cli@latest deploy --prod

# Deploy PR preview
npx eas-cli@latest deploy
```

## EAS Configuration

Standard `eas.json` for production deployments:

```json
{
  "cli": {
    "version": ">= 16.0.1",
    "appVersionSource": "remote"
  },
  "build": {
    "production": {
      "autoIncrement": true,
      "ios": {
        "resourceClass": "m-medium"
      }
    },
    "development": {
      "developmentClient": true,
      "distribution": "internal"
    }
  },
  "submit": {
    "production": {
      "ios": {
        "appleId": "[email protected]",
        "ascAppId": "1234567890"
      },
      "android": {
        "serviceAccountKeyPath": "./google-service-account.json",
        "track": "internal"
      }
    }
  }
}
```

## Platform-Specific Guides

### iOS

- Use `npx testflight` for quick TestFlight submissions
- Configure Apple credentials via `eas credentials`
- See ./reference/testflight.md for credential setup
- See ./reference/ios-app-store.md for App Store submission

### Android

- Set up Google Play Console service account
- Configure tracks: internal → closed → open → production
- See ./reference/play-store.md for detailed setup

### Web

- EAS Hosting provides preview URLs for PRs
- Production deploys to your custom domain
- See ./reference/workflows.md for CI/CD automation

## Automated Deployments

Use EAS Workflows for CI/CD:

```yaml
# .eas/workflows/release.yml
name: Release

on:
  push:
    branches: [main]

jobs:
  build-ios:
    type: build
    params:
      platform: ios
      profile: production

  submit-ios:
    type: submit
    needs: [build-ios]
    params:
      platform: ios
      profile: production
```

See ./reference/workflows.md for more workflow examples.

## Version Management

EAS manages version numbers automatically with `appVersionSource: "remote"`:

```bash
# Check current versions
eas build:version:get

# Manually set version
eas build:version:set -p ios --build-number 42
```

## Monitoring

```bash
# List recent builds
eas build:list

# Check build status
eas build:view

# View submission status
eas submit:list
```

Overview

This skill packages a practical guide and tooling for deploying Expo apps with EAS to iOS App Store, Android Play Store, web hosting, and API routes. It focuses on build, submit, and hosting commands plus configuration examples for production and CI/CD. The content helps teams automate releases, manage credentials, and monitor build and submission status.

How this skill works

It explains how to initialize EAS, create and tune eas.json build and submit profiles, and run platform-specific build and submit commands. The skill describes web deployment via EAS Hosting, TestFlight flow for iOS, Google Play service account setup for Android, and CI/CD workflows that trigger builds and submissions. It also shows commands for version management and monitoring builds and submissions.

When to use it

  • Preparing production releases for iOS and Android using EAS
  • Setting up web deployments and PR preview URLs with EAS Hosting
  • Automating builds and submissions in CI/CD pipelines
  • Managing credentials and store metadata for App Store and Play Store
  • Checking build and submission status during release troubleshooting

Best practices

  • Initialize eas.json and define clear production and development profiles with autoIncrement where appropriate
  • Keep Apple and Google credentials secure and configure them via eas credentials and service account JSON files
  • Use CI workflows to run reproducible builds and separate build and submit jobs for safer rollouts
  • Use TestFlight and Play Store tracks (internal → closed → open → production) for staged rollouts
  • Monitor builds and submissions (eas build:list, eas build:view, eas submit:list) and use explicit versioning when needed

Example use cases

  • Run npx eas-cli build -p ios --profile production and submit to App Store Connect for a new iOS release
  • Build Android production artifact and submit to Play Store with npx eas-cli build -p android --profile production --submit
  • Deploy a web version and PR preview using npx expo export -p web followed by npx eas-cli deploy
  • Create CI pipeline that triggers build jobs on main and subsequent submit jobs after successful builds
  • Use eas build:version:get and eas build:version:set to inspect or force version numbers during a hotfix

FAQ

Do I need an EAS account to use these commands?

Yes. You should install and log in to the EAS CLI (eas-cli) and configure your project with npx eas-cli init to use EAS build and hosting services.

How do I handle app store credentials?

Use eas credentials to manage Apple credentials and a Google Play service account JSON for Android. Store sensitive keys securely and reference them in eas.json or CI secrets.