Problem
The web variant of ErrorBoundary (src/components/ErrorBoundary/index.tsx) only called Log.alert(...) when a render error was caught — it never reported to Sentry. The native variant already adds an errorInfo breadcrumb and calls Sentry.captureException, so render errors caught on web (e.g. React error #185 "Maximum update depth exceeded") were invisible in Sentry.
Solution
Mirror the native ErrorBoundary's Sentry reporting into the web variant by adding Sentry.addBreadcrumb and Sentry.captureException calls in the logError handler. The existing Log.alert call is unchanged, and native behavior is unaffected since index.native.tsx is not modified.
PR
#91405
Issue Owner
Current Issue Owner: @sosek108
Problem
The web variant of
ErrorBoundary(src/components/ErrorBoundary/index.tsx) only calledLog.alert(...)when a render error was caught — it never reported to Sentry. The native variant already adds anerrorInfobreadcrumb and callsSentry.captureException, so render errors caught on web (e.g. React error #185 "Maximum update depth exceeded") were invisible in Sentry.Solution
Mirror the native ErrorBoundary's Sentry reporting into the web variant by adding
Sentry.addBreadcrumbandSentry.captureExceptioncalls in thelogErrorhandler. The existingLog.alertcall is unchanged, and native behavior is unaffected sinceindex.native.tsxis not modified.PR
#91405
Issue Owner
Current Issue Owner: @sosek108