Release Health | Zyeon UI

Preview in your theme

ready · 4.3.0-rc.2 is 0.67 pp down on 4.2.1 and under both bars, so the panel says what would clear it. Pick a row (or arrow up and down inside the list) to re-read another version — onSelectVersion last fired for nothing yet

Release health

iOS · 30-day window · sessions from the crash reporter

Below the bar

Bar: 99.20% crash-free sessions · 99.50% crash-free users.

Adoption

Share of the 82,060 sessions listed here, rounded to whole points that add up to 100.

Newest first by semantic-version precedence.

4.3.0-rc.2

released Aug 14, 2026

Crash-free sessions98.74%below the 99.20% bar-0.67 pp vs 4.2.1

Crash-free users99.10%below the 99.50% bar-0.58 pp vs 4.2.1

3% of the sessions listed here · 2,140 sessions · 890 users. The reporter puts this build at 1.8% of the whole fleet, which counts versions this payload does not list.

What it would take to clear the bar

About 27 of 2,140 sessions crashed. The 99.20% bar allows 17 at this volume, so 10 crashed sessions have to go — or about 1,235 more sessions have to land clean at the same crash count.

About 8 of 890 users hit a crash. The 99.50% bar allows 4, so 4 of them have to stop crashing.

The figures above hold the volume where it is; a rate measured over a moving denominator also drifts on its own, without a single crash being fixed.

Top crash groups

31 events across 4 listed groups; the shares below are of those events.

NullPointerException in FeedAdapter.bind14 events · 45%New in this version
IllegalStateException · Fragment not attached to a context9 events · 29%Carried over since 4.2.0
OutOfMemoryError while decoding a 12 MP upload5 events · 16%Carried over since 4.1.3
ANR · main thread blocked in SyncWorker.doWork3 events · 10%Carried over since 4.3.0-rc.1

Counts are crash events, and one session can log more than one, so they do not add up to a number of crashed sessions. This is a top list, not every group on the version.

ready · the inputs that break the arithmetic: a calendar version that is not semver (so the whole list falls back to release-date order), a build with 0 sessions that reads as not measurable rather than a perfect 100%, a release sitting exactly on both bars, a 100% session bar no crashing build can grow its way over, and crash groups first seen on a later version and on a nightly build that cannot be ordered at all

Edge payload

Android · mixed version schemes · a 100% session bar

Below the bar

Bar: 100.00% crash-free sessions · 99.50% crash-free users.

Adoption

Share of the 24,500 sessions listed here, rounded to whole points that add up to 100.

Newest first by release date — not every version here is a semantic version, so precedence cannot order them.

2026.08.1

released Aug 16, 2026

Crash-free sessions99.89%below the 100.00% bar+0.39 pp vs v4.4.0

Crash-free users99.74%at or above the 99.50% bar+0.02 pp vs v4.4.0

4% of the sessions listed here · 900 sessions · 380 users.

What it would take to clear the bar

About 1 of 900 sessions crashed. The 100.00% bar allows 0 at this volume, so 1 crashed session has to go — and no amount of extra clean traffic can lift the rate while a single session still crashes.

The figures above hold the volume where it is; a rate measured over a moving denominator also drifts on its own, without a single crash being fixed.

Top crash groups

1 event across 1 listed group; the shares below are of those events.

IndexOutOfBoundsException in StoryPager1 event · 100%Carried over since v4.4.0

Counts are crash events, and one session can log more than one, so they do not add up to a number of crashed sessions. This is a top list, not every group on the version.

loading · the skeleton keeps the real anatomy (header, release rows, the two rate tiles) so nothing jumps when the counts land

empty · the reporter answered, but no build has sessions in this window — no rates, no bar comparison, nothing asserted

No releases in this window

Once a build reports sessions, this panel compares its crash-free rates against the bar and lists the crash groups behind them.

error · onRetry is wired to real local state — requested 0 times. No partial rates are shown, because a half-loaded release reads as a healthy one

Couldn't load release health

The crash reporter did not respond. No partial rates are shown, because a half-loaded release reads as a healthy one.

Loading preview…

This component is part of Pro

The install command, prompt and concept map are included with a Pro license — one purchase unlocks every Pro component, forever.

Unlock with Pro