TraceRN

Press ⌘K anywhere to search

Bad release

Catch a bad React Native release early with release tags, crash-free health, and CLI source maps

Version 1.4.2 ships at noon. By evening crash-free sessions drop. Without a release tag you cannot tell which build is bleeding.

What to instrument

  1. Pass the same release string into TraceRN.init that you use in CI
  2. Keep enableSessionHeartbeat: true for accurate crash-free rates
  3. Upload source maps for that release via @tracern/cli
  4. Watch release health after rollout
javascript
TraceRN.init({
  apiKey: "trn_live_xxxxxxxx",
  environment: "production",
  release: process.env.EXPO_PUBLIC_APP_VERSION ?? "1.4.2",
  enableSessionHeartbeat: true,
  enableAutoErrorCapture: true,
});
bash
npx @tracern/cli sourcemaps upload \
  --release 1.4.2 \
  --file ./dist/main.js.map \
  --project "$TRACERN_PROJECT_ID" \
  --token "$TRACERN_TOKEN"

What you see in TraceRN

  1. Compare crash-free % across releases on release health
  2. Crash groups show first-seen release and breadcrumb path — triage in Crashes
  3. Set regression digests in alerts

Related

Releases · Source maps · Crash grouping

Last updated · TraceRN docs