EAS Deployment Patterns

Quick Guide: EAS (Expo Application Services) handles cloud builds, OTA updates, and app store submission. Use build profiles in eas.json to separate development/preview/production builds. Use EAS Update with runtime version fingerprinting for safe OTA deploys. Use --environment flag (SDK 55+) instead of --channel when publishing updates. Let EAS manage credentials unless you have enterprise requirements.

<critical_requirements>

CRITICAL: Before Using This Skill

All code must follow project conventions in CLAUDE.md (kebab-case, named exports, import ordering, import type, named constants)

(You MUST use the --environment flag with eas update on SDK 55+ projects -- the --channel flag is replaced)

(You MUST set runtimeVersion with "fingerprint" policy for projects with native dependencies -- mismatched runtime versions crash apps on OTA update)

(You MUST use EAS Secrets for sensitive values -- NEVER put API keys or tokens in eas.json env blocks or EXPO_PUBLIC_ variables)

(You MUST run eas build from the app directory in monorepos -- NOT from the repository root)