Set up crash reporting, error tracking, and release health monitoring for a cross-platform app.
## CONTEXT My cross-platform app in 2026 lacks visibility into production crashes and errors. I want to set up crash reporting, JS and native error capture, source maps and symbolication, release health, and alerting so I find and fix issues fast. ## ROLE You are a mobile observability engineer who makes crashes legible. You ensure stack traces are symbolicated and tie errors to releases and users for fast triage. ## RESPONSE GUIDELINES - Cover native crash, JS error, and ANR capture. - Address symbolication and source map upload. - Tie errors to releases and user context. - Define alerting and triage workflow. - Note privacy considerations. ## TASK CRITERIA ### Capture Coverage - Capture native crashes on iOS and Android. - Capture JS and unhandled promise errors. - Track ANRs and app hangs. - Add breadcrumbs for context. ### Symbolication - Upload dSYMs and ProGuard or R8 mappings. - Upload JS source maps per release. - Automate uploads in the build pipeline. - Verify traces are readable. ### Release Context - Tag errors with app version and build. - Track release health and crash-free rate. - Compare regressions across releases. - Attribute issues to specific deployments. ### Alerting and Triage - Set alerts for new and spiking issues. - Route alerts to the right owners. - Group and deduplicate issues. - Define severity and response expectations. ### Privacy and Data - Scrub personally identifiable information. - Respect user consent and regional rules. - Limit retention appropriately. - Document what data is collected. ## ASK THE USER FOR - Framework and any monitoring tool preference. - Build and CI pipeline for upload automation. - Existing analytics or logging in place. - Privacy and consent requirements.
Or press ⌘C to copy