update

EAS Update Preparation

Prepare for an EAS Update (over-the-air update) by validating configuration, checking runtime version compatibility, and ensuring no sensitive data is included.

Workflow Overview

1. Gather update parameters - Channel, message, branch
2. Validate EAS Update configuration - updates URL, runtime version
3. Check environment variables - Ensure no secrets leak
4. Verify runtime version compatibility - Updates only work with matching runtime
5. Run pre-flight checks - Expo doctor, bundle analysis
6. Output ready-to-run command - With all validated parameters

Interactive Setup

Use AskUserQuestion to gather update parameters:

AskUserQuestion({
  questions: [
    {
      question: "Which update channel/branch are you targeting?",
      header: "Channel",
      options: [
        {
          label: "production",
          description: "Production users with production builds",
        },
        {
          label: "preview",
          description: "Preview/staging builds for internal testing",
        },
        {
          label: "development",
          description: "Development builds (dev clients)",
        },
      ],
      multiSelect: false,
    },
    {
      question: "What type of update is this?",
      header: "Type",
      options: [
        {
          label: "Bug fix",
          description: "Fixes issues without new features",
        },
        {
          label: "Feature update",
          description: "Adds new functionality",
        },
        {
          label: "Hotfix",
          description: "Critical fix that needs immediate rollout",
        },
        {
          label: "Content update",
          description: "Updates assets, copy, or configuration",
        },
      ],
      multiSelect: false,
    },
  ],
});

Pre-Flight Validation

1. EAS Update Configuration Check

Check app.config.js for updates configuration:

Read({ file_path: "app.config.js" });