Playbooks
React Native observability playbooks: solve checkout failures, stuck screens, offline issues, and bad releases — not only crashes
TraceRN is mobile observability for React Native: see what the user did, what the phone did, and what broke — in real time. Crashes matter, but most support pain is a failed payment, a stuck spinner, a slow API, or a bad release — with no stack trace.
Feature map
| Layer | What you use | Problems it catches |
|---|---|---|
| Structured logs | log / warn / error + context | Business failures (declined card, empty state) |
| Trail | Breadcrumbs, trackScreen, network / AppState | “How did we get here?” |
| Identity | setUser, tags, release, environment | Which user / build / env |
| Crashes | Auto capture + crash groups | Hard failures |
| Health | Sessions + release health | Is 1.4.2 worse than 1.4.1? |
| Voice | captureFeedback | Soft failures users report |
| Ops | Alerts, webhooks, log viewer | React before tickets pile up |
Start here
- What to log — taxonomy and a minimum instrumentation checklist
- Pick a scenario below and wire it in your app
- Confirm the same story in the log viewer
Scenarios
| Playbook | When to open it |
|---|---|
| Checkout failed | Payment / API failure without a crash |
| Blank or stuck | White screen or infinite spinner |
| Slow or offline | Latency regressions and offline queue |
| Bad release | Ship with release tags and crash-free health |
| User said it’s broken | Feedback when there is no stack |
Related guides
Custom logs · Breadcrumbs · Releases · User feedback · SDK methods
Last updated · TraceRN docs