eas-update-insights

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

Updated Sep 6, 2026
One-click install
npx skills add https://github.com/sombek/fitness-guidance-app --skill eas-update-insights-sombek
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eas-update-insights
Source: https://github.com/sombek/fitness-guidance-app/tree/main/mobile/.agents/skills/eas-update-insights
Command: npx skills add https://github.com/sombek/fitness-guidance-app --skill eas-update-insights-sombek

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill 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—crash rates, install counts, unique users, and the split between embedded and OTA users—without opening the expo.dev dashboard. ## 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-level adoption: Run eas channel:insights to compare embedded-build users versus OTA users and rank the most popular updates per channel and runtime version. - CI gating and regression detection: All commands support --json --non-interactive for scripting, enabling automated rollout monitoring and crash-rate thresholds. - Use Case: After publishing a fix to the production branch, grab the latest group ID with eas update:list, then check whether the crash rate exceeds 1% in the last 24 hours before widening the rollout. ## Quick Start Ask the assistant to check whether the latest EAS Update published to the production channel 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 per-platform crashRatePercent, computed as failedInstalls divided by total installs, plus a daily breakdown of installs 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.

Does eas update:insights support JSON output for scripting?

Yes, all insights commands support `--json --non-interactive` for machine-readable output. The JSON includes totals, payload sizes, and daily time series that can be filtered with jq for CI gating or monitoring scripts.

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

Fresh publishes may show zeros while the metrics pipeline catches up. Also, installs count manifest downloads, and confirmed runs only register 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 double-count 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.

Is EAS Update insights a free Expo feature?

No, EAS Update is a paid Expo Application Services product with free-tier limits. Update delivery and the metrics behind these commands count against your plan's EAS Update usage, so review expo.dev/pricing.