All SkillsGet Started Free
Eas Update Insights
Check the health of published EAS Updates: crash rates, install/launch counts, unique users, payload size, and the split between embedded and OTA users per channel. Use when the user asks how an update is performing, whether a rollout is healthy, how many users are on the embedded build vs OTA, or wants to gate CI on update health.
MCP get_skill({ skillId: "eas-update-insights-9c716410" })Use this skill with your agent
Create a free account and connect via MCP
# EAS Update Insights Query the health of published EAS Updates directly from the CLI: launches, failed launches, crash rates, unique users, payload size, the embedded-vs-OTA user split per channel, and the most popular updates per runtime version. The data is the same data that powers the update and channel detail pages on expo.dev; these commands expose it in the terminal in human and JSON form. ## When to use this skill Use this when the user wants to assess the health or adoption of a published EAS Update: crash rates, install counts, unique users, bundle size, or the split between embedded and OTA users on a channel. Example prompts: - "How is the latest update doing?" - "Is the latest update healthy?" - "Is the new release crashing more than the last one?" - "How many users are on the latest update vs the embedded build?" - "Which update is most popular on production right now?" - "How big is our update bundle?" Also fits: post-publish rollout monitoring and regression detection. Don't use when the user needs per-user crash detail or device-level reporting; this skill only exposes aggregate EAS metrics. ## Prerequisites - `eas-cli` installed (`npm install -g eas-cli`). - Logged in: `eas login`. - For `channel:insights`: run from an Expo project directory (the command resolves the project ID from `app.json`). `update:insights` only needs a login. ## Commands at a glance | Command | Purpose | |---|---| | `eas update:list` | Discover recent update groups, their `group` IDs, and branch names | | `eas update:insights <groupId>` | Per-platform launches, failed launches, crash rate, unique users, payload size, daily breakdown | | `eas update:view <groupId> --insights` | Update group details + the same metrics appended | | `eas channel:insights --channel <name> --runtime-version <version>` | Embedded/OTA user counts, most popular updates, cumulative metrics for a channel + runtime | All of these support `--json --non-interactive` for programmatic parsing. ## Discovering IDs Before querying insights for an update group, you need its `group` ID. Use `eas update:list` with either `--branch <name>` (updates on that branch) or `--all` (updates across all branches). Always pass `--json --non-interactive` when running non-interactively; without a branch/`--all` flag the command will otherwise prompt for a branch selection: ```bash # Latest group id across all branches eas update:list --all --json --non-interactive | jq -r '.currentPage[0].group' # Latest group id on a specific branch eas update:list --branch production --json --non-interactive | jq -r '.currentPage[0].group' ```
#react-native#expo#react#native#best#practiceseas-cli