12 March 2026
Crash clusters that only appear in one store
The Slack thread titled “everything is on fire” is often a single vendor binary that never existed on web.
When a crash reporter fans out a new cluster, the instinct is to write an incident as if every client shares a process. Product, support, and store review teams then inherit a sentence that is too wide. Cross-Platform App Reporting starts by asking which binary, which OS band, and whether the web client even loads the same library.
Split before you name
Draw three columns: iOS, Android, web. Place the stack signature in only the columns that can compile it. If the symbol is a Kotlin package, web does not belong in the headline. If the cluster is a WebView bridge, native-only dashboards will look calm while web looks injured. That disagreement is information, not a tracking failure.
We practise this split in Field Ledger week three with a redacted export. People who skip it publish “platform-wide instability” and then spend Friday retracting it for desktop browsers.
Coverage is part of the incident
Store roll-outs are staggered. A 12% staged release on Play is not a 12% staged release on the App Store. Your crash-free session rate for “today” may mix users who cannot have the new code with users who must have it. The weekly pack should say so in the coverage line, not in a footnote nobody reads.
If you cannot get a staged percentage from the console in time, write “unknown mix” rather than a precise-looking rate. Precision without mix is a costume.