eas-update-insights

Query crash rates, installs, and adoption metrics for published EAS Updates via the eas-cli.

16|1|Updated May 5, 2026
One-click install
npx skills add https://github.com/AIBiz-Automatyzacje/workspace-template-mobile --skill eas-update-insights-aibiz-automatyzacje
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eas-update-insights
Source: https://github.com/AIBiz-Automatyzacje/workspace-template-mobile/tree/main/.claude/skills/eas-update-insights
Command: npx skills add https://github.com/AIBiz-Automatyzacje/workspace-template-mobile --skill eas-update-insights-aibiz-automatyzacje

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires eas-cli, and includes references (resource) components.

What problem does it solve? After publishing an over-the-air update with EAS Update, teams lack terminal access to rollout health data and must manually check the expo.dev dashboard to know whether an update is crashing, how many users adopted it, or how large the payload is. ## Core Features & Use Cases - Update health checks: Run eas update:insights <groupId> to get per-platform launches, failed installs, crash rate, unique users, and payload size with daily breakdowns. - Channel adoption analysis: Run eas channel:insights to compare embedded-build users versus OTA users and rank the most popular updates per channel and runtime version. - Scriptable JSON output: All commands support --json --non-interactive for CI gating, regression detection, and release-note generation via jq. - Use Case: After publishing a fix to the production channel, wait for adoption, then check whether the crash rate exceeds 1% in the last 24 hours and decide whether to roll back. ## Quick Start Ask the assistant to check whether the latest update published to the production channel is healthy and show its crash rate per platform.

Frequently Asked Questions about eas-update-insights

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check the crash rate of an EAS Update?

Run `eas update:insights <groupId>` with the update group ID from `eas update:list`. The output shows per-platform installs, failed installs, and crashRatePercent, with `--days N` or `--start`/`--end` to control the time window.

How to see how many users are on OTA vs embedded build?

Run `eas channel:insights --channel <name> --runtime-version <version>` from an Expo project directory. It returns embeddedUpdateTotalUniqueUsers, otaTotalUniqueUsers, and the most popular updates ranked by unique users.

Can I use EAS Update insights in CI scripts?

Yes, all insights commands support `--json --non-interactive` for machine-readable output. Pipe the JSON through jq to gate deployments on metrics like crashRatePercent exceeding a threshold.

Why does eas update:insights show zeros right after publishing?

Fresh publishes show zeros while the metrics pipeline catches up, and installs only register on the user's next update check, typically up to 24 hours later. Wait for adoption time before evaluating health.

What are the limitations of EAS Update crash reporting?

Crashes are self-reported on the next update check, so crashes that kill the process before recovery never appear. Unique users may also be double-counted across iOS and Android for the same publish.