domains / families / devops / eas-update-insights

eas-update-insights

authentic

Check the health of published EAS Update: 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.

When to use

• "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?"

When not to use

• **Unique users across platforms** may double-count users who run the same publish on both iOS and Android. The same caveat applies to `otaTotalUniqueUsers` in channel insights, which is a sum over `mostPopularUpdates`.
• **Fresh publishes** may show zeros for a short period while the metrics pipeline catches up.
• **Installs are downloads, not launches**: the `installs` / "Launches" field counts users who downloaded the manifest and launch asset. A confirmed run only registers on the user's *next* update check (typically up to 24h later, depending o…
• **Crashes are self-reported**: `failedInstalls` / "Crashes" counts updates that errored during install/launch and were reported on the next update check. Crashes that don't trigger an update request (e.g. process kill before recovery) won'…

Skill page

Source