eas-update-insights

Query crash rates, adoption, and embedded-versus-OTA metrics for published EAS Updates via eas-cli.

Updated Sep 11, 2026
One-click install
npx skills add https://github.com/CYRUS-pinto/pi-bot --skill eas-update-insights-cyrus-pinto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eas-update-insights
Source: https://github.com/CYRUS-pinto/pi-bot/tree/main/.agents/skills/eas-update-insights
Command: npx skills add https://github.com/CYRUS-pinto/pi-bot --skill eas-update-insights-cyrus-pinto

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? After publishing an EAS Update, teams lack a quick terminal-based way to verify rollout health, forcing them to open the Expo dashboard to check crash rates, adoption counts, and whether users are on the embedded build or an OTA update. ## Core Features & Use Cases - Update health checks: Run eas update:insights <groupId> to get per-platform launches, failed installs, crash rate, unique users, payload size, and a daily time series. - Channel-level adoption: Run eas channel:insights to compare embedded-build users versus OTA users and rank the most popular updates for a channel and runtime version. - CI gating and regression detection: All commands support --json --non-interactive output for scripting, such as failing a pipeline when crash rate exceeds a threshold. - Use Case: After publishing a fix to the production branch, grab the latest group ID with eas update:list, then check crashRatePercent per platform to confirm the rollout is healthy before widening it. ## Quick Start Ask the assistant to check whether the latest update published to the production branch is healthy, including its crash rate and user adoption.

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>` after finding the group ID with `eas update:list`. The output includes `crashRatePercent` per platform, computed as failed installs divided by total installs, plus a daily breakdown of launches and failures.

How to see embedded vs OTA users on an EAS channel?

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 extract fields like crash rate and gate your pipeline, for example failing when `crashRatePercent` exceeds a threshold.

Why does eas update:insights show zero installs after publishing?

Fresh publishes may show zeros while the metrics pipeline catches up. Also, installs count manifest downloads, and a confirmed run only registers on the user's next update check, typically up to 24 hours later.

What are the limitations of EAS Update insights metrics?

Unique users may be double-counted across iOS and Android, and `otaTotalUniqueUsers` sums only the top-N updates so it can undercount. Crashes are self-reported on the next update check, so crashes without a subsequent update request never appear.