Crash-free sessions regression on Android TV following app 3.4.1
98.71%
from 99.30% · −0.59pp
46,120
Android TV 12/13 · all tenants · app 3.4.1
4,120
Modelled over 30 days
21h 24m ago
27 Aug 16:56 UTC
App and player quality. Crash, start failure, TTFF, version regressions.
Triage
What is happening
Crash-free sessions on Android TV fell 0.59pp within 36 hours of the 3.4.1 rollout, against a stable 30-day baseline. Crashlytics attributes 71% of the new crashes to one signature in the playback surface. The novelty detector flagged this signature as previously unseen. Retention consequence is already measurable: D7 for users who crashed at least once is 22.4pp below the cohort baseline.
Hold the 3.4.1 Android TV rollout at its current share and request the symbolised stack for signature PlaybackSurface.onSurfaceDestroyed.
What fired, and against what
Each signal names the detector that produced it, the value it saw and the value it expected. This is the part a vendor will try to take apart, so it is stated in full.
- S-8790
Crash-free sessions
FIRE98.71%expected 99.30%−0.59pp- Slice
- Android TV · app 3.4.1
- Detector
- Threshold rule
- Confidence
- 96%
- Users
- 46,120
- Detected
- 21h 24m ago
- S-8794
New crash signature
FIRE3,412 eventsexpected 0 eventsnew- Slice
- PlaybackSurface.onSurfaceDestroyed
- Detector
- Novelty detection
- Confidence
- 99%
- Users
- 32,740
- Detected
- 21h 2m ago
- S-8801
D7 retention
FIRE38.2%expected 60.6%−22.4pp- Slice
- Android TV · crashed ≥ 1×
- Detector
- Churn model
- Confidence
- 88%
- Users
- 46,120
- Detected
- 10h 40m ago
Evidence
The governed query each detector ran, the rows it returned, and the fact grain underneath. Every table exports.
Crash-free sessions by app version, Android TV
SELECT app_version, metric('crash_free_sessions') AS observed, metric('sessions') AS sessions
FROM semantic.session
WHERE platform = 'Android TV' AND day >= now() - interval '7 days'
GROUP BY app_version ORDER BY app_version DESC| app version | crash-free | sessions | rollout |
|---|---|---|---|
| 3.4.1 | 98.71% | 1,284,110 | 42% |
| 3.4.0 | 99.28% | 1,641,882 | 51% |
| 3.3.2 | 99.34% | 212,440 | 7% |
Top new crash signatures since 3.4.1
SELECT signature, events, affected_users, first_seen FROM detect.novelty(source => 'crashlytics', window => '7 days') ORDER BY events DESC LIMIT 3
| signature | events | users | first seen |
|---|---|---|---|
| PlaybackSurface.onSurfaceDestroyed | 3,412 | 32,740 | 26 Aug 09:12 |
| DrmSessionManager.acquire | 612 | 5,890 | 26 Aug 11:40 |
| CatalogueRail.bind | 204 | 2,110 | 27 Aug 03:22 |
Route an evidence ticket
Pre-filled from the finding and addressed by fault domain. Editable before it goes.
- Crash-free sessions by app version, Android TV (3 rows)
- Top new crash signatures since 3.4.1 (3 rows)
Timeline
- Detected27 Aug 16:56 UTC
Threshold rule on Crash-free sessions — 98.71% against 99.30%
Detection engine - Acknowledged27 Aug 19:18 UTC
142 minutes after detection, against a 60-minute target
SimpleStream — release engineering - Routed27 Aug 19:20 UTC
SimpleStream — Jira Service Desk — SSD-4471
A. Drobinoha - Response27 Aug 23:40 UTC
Acknowledged at 14h. SimpleStream asked for the symbolised stack, which was in the original bundle.
SimpleStream — Jira Service Desk
Related findings
Nothing related. For a first occurrence that is expected; for a recurring defect it usually means the related-findings link has not been established rather than that none exists.
Clustered support tickets
- App closes itself on my TV19h 40m ago
ZD-48044 · Praia Telecom BR
- Crashes when I press play15h 2m ago
ZD-48098 · Sur Digital CL