Bug tracking for React Native — session replay, console + HAR (2026)
Capture Expo Web and react-native-web bugs with an rrweb replay, console, and network HAR. Understand the redbox-vs-production gap and the native-app boundary.
What React Native teams ship with BugMojo
React Native for Web is documented as "a compatibility layer between React DOM and React Native" that "uses React DOM to accurately render React Native compatible JavaScript code in a web browser." That one sentence is why a Chrome extension is relevant to a React Native team at all: the Expo Web or react-native-web build is real browser HTML, not a native view tree, so an rrweb DOM replay, console capture, and a network HAR all work on it exactly as they would on any React website. This page is about the web target of a universal React Native project — and only that target.
The core asymmetry to plan around is in the official debugging docs: the Dev Menu, LogBox, and React Native DevTools are all "disabled in release (production) builds." The redbox a fatal error throws and the yellowbox a warning shows are development surfaces that simply do not exist for end users. A production React Native Web bug arrives as a blank screen, a frozen UI, or a silently failed request with no overlay to read, which is why you need an external capture layer rather than the in-app error UI. This guide is for teams shipping Expo Web and react-native-web in 2026: what the web-only failures look like, how to capture the exact failing session, and where the native-app boundary sits.
React Native gotchas
Framework-specific failure modes engineers actually ship through. Each is hard to spot in a screenshot and obvious in a session replay.
Common React Native bugs
Real React Native bug patterns — the symptom you will see in a report and the fix that actually works.
Production web bug with no redbox to read
Symptom: In a development build the failure showed a redbox you could read; in the deployed Expo Web build the screen just goes blank or freezes with nothing on screen explaining why.
Fix: Reproduce the issue in the deployed web build and capture it. Because LogBox is disabled in release builds, the answer is not on screen — it is in the console messages React still emits and the network request that fed the bad state, both of which the captured session preserves alongside an rrweb replay you can scrub.
// LogBox / Dev Menu / RN DevTools are disabled in release builds.
// A prod web error has no overlay — capture console + network instead:
// rrweb DOM replay -> what the user saw, frame by frame
// console log -> the warning/error React emitted
// network HAR -> the request that produced the bad stateStyle renders correctly on iOS/Android but breaks under react-native-web
Symptom: A component looks right in the native app but is misaligned, clipped, or mis-shadowed only in the Expo Web build, and a native screenshot shows nothing wrong.
Fix: This is a web-only divergence: react-native-web renders through React DOM, so the failing artifact is browser HTML/CSS, not a native view. Capture the web session and inspect the DOM tree and computed layout at the failure instant in the replay rather than guessing from a native screenshot that cannot reproduce the web render.
// react-native-web is "a compatibility layer between React DOM and
// React Native" — the rendered output is real DOM. So a web-only
// layout bug is inspectable as ordinary HTML in the captured replay,
// even though the same code looks fine on the native target.Universal fetch resolves differently on the web build
Symptom: A request that returns usable data on device returns a different shape, a CORS failure, or an empty body only on the web build, and the UI silently renders the bad state.
Fix: Capture the web session so the network HAR carries the exact request, its headers, and the response that fed the component. Pair it with the console for any warning React logged. You then reproduce the precise sequence — request in, bad state out — instead of inferring it from a frozen screenshot.
// The web target ships standard browser HTML rendered via React DOM,
// so the request waterfall is a normal HAR. Capture shows:
// request URL + method + headers (incl. credentials/CORS)
// response status + body the component actually receivedBugMojo vs alternatives
The honest comparison — where BugMojo wins, and where another tool might serve you better.
| Feature | BugMojo | Sentry React Native SDK |
|---|---|---|
| DOM session replay of the exact failing web session | ✅ rrweb-based, on-demand | ⚠️ web replay is sampled; RN replay is native-focused |
| Console + network HAR from the user's web session | ✅ full HAR + console, no SDK | ⚠️ breadcrumbs + events, needs SDK instrumentation |
| Captures the Expo Web / react-native-web target with zero code changes | ✅ browser extension, no npm package | ❌ requires the Sentry SDK in the app |
| Native iOS/Android crash monitoring, source-mapped + symbolicated | ❌ web target only in V1 (native is V2) | ✅ mature native + JS error monitoring |
| Always-on production error aggregation tied to releases | ❌ on-demand capture, not always-on | ✅ Sentry is more complete here |
| MCP server: Claude Code / Cursor read the bug in the IDE | ✅ captured bug is a first-class AI-agent assignee | ❌ none |
| Zero-setup Quick Capture | No project, no SDK | Account / SDK required |
BugMojo records the DOM, console, and network — then ships a one-click ticket with the full replay attached. No SDK, no setup.
Try BugMojo freeFrequently asked questions
Frequently asked questions
Sources
- React Native — Debugging Basics (LogBox, RN DevTools; disabled in release/production builds) — Meta / React Native (official docs) (2025)
- Expo — Errors and warnings (Redbox = fatal error, Yellowbox = warning, LogBox) — Expo (official docs) (2025)
- React Native for Web — Docs ("a compatibility layer between React DOM and React Native") — react-native-web (Nicolas Gallagher, official docs) (2025)
- Develop websites with Expo (Metro + react-native-web, static or client rendering) — Expo (official docs) (2025)
- React Native 0.76 — New Architecture by default; React Native DevTools replaces Chrome DevTools + Flipper — Meta / React Native (official blog) (2024-10-23)
- 2024 Stack Overflow Developer Survey — Technology (React Native 8.4% all / 9.0% professional) — Stack Overflow (2024)