Releases

Release health shows whether a version is stable: how many sessions it served, how many ended in a crash, and how that compares with the release before it.

Crash-free ratelink

The headline number is the share of sessions that ended without a crash. It is the fastest way to answer "is this version worse than the last one", because it is normalised by usage. A release with more users naturally produces more errors without necessarily being less stable.

Making releases meaningfullink

Set a release identifier when you initialise the SDK, and use the same string when uploading symbols and recording deployments. That single value ties crashes, symbols and deploys to one version.

A common cause of a blank Releases tab is an SDK reporting no release, or reporting a value that changes on every build.

A caveat on mobile crash-free ratelink

Mobile sessions are finalised on the launch after the one that ended. A run killed by the operating system for memory pressure leaves no crash artifact, so it is finalised as exited rather than crashed. Mobile crash-free rate therefore reads slightly optimistic. See Mobile for the full detail.