Nalya/Blog
About
Product·5 min read

Error tracking that triages itself: crashes, ANRs and errors in one ranked list

Every live app crashes. The difference between a blip and a one-star avalanche is how fast you notice, how quickly you understand what broke, and whether you catch the regression when it comes back. Nalya's Issues module is now live for every connected app, and it handles all three.

One list, three feeds

Crash data lives in too many places. Play Console has vitals, your analytics tool has exceptions, and whatever your app reports directly lives somewhere else again. Issues folds three feeds into one ranked list:

  • Google Play vitals - crash and ANR clusters straight from the Play Developer Reporting API, with zero integration work. If your app is connected to Nalya, this feed is already flowing.
  • PostHog error tracking- if your app already reports exceptions to PostHog, Nalya reads the same issues through your project's API key and folds them in.
  • The Nalya SDK - apps using the Nalya client SDK report crashes directly, stack traces included - which also covers iOS, where Apple offers no crash API to pull from.

Each issue is grouped (one row per distinct crash, not one per occurrence) and ranked by the number that actually matters: how many users it hurts.

Triage in plain language

A stack trace tells you where the app died, not what to do about it. For every issue with real impact, Nalya drafts a triage: what broke in one or two plain sentences, a severity call, and the first thing to try. When the signal is too thin to name a cause, she says exactly that instead of inventing one.

Statuses that respect reality

Mark an issue resolved and it leaves the list - but if the same crash shows up again after your fix, it re-opens on its own and you get told. Mark it mutedand it stays gone, forever, no matter how often it fires - for the errors you've decided to live with. No zombie dashboards, no wishful thinking.

Why vitals deserve this attention

Google folds crash and ANR rates into how your app ranks and whether it gets recommended - cross the bad-behavior thresholds and Play quietly buries you. We wrote a practical guide to Android vitals if you want the thresholds and mechanics; the short version is that a crash spike costs you installs before it costs you reviews.

Drivable from your coding agent

The same issues are exposed over Nalya's MCP server: list_issues, get_issue (triage and stack traces included), set_issue_status and sync_issues. Ask Claude Code "what's crashing the most right now?", open the stack, fix the bug, and mark it resolved - without leaving your editor.

Issues is live now on every tier's console during the open beta. Connect your app once and the Play vitals feed starts on its own - the rest joins as you wire it up.