Error was not tracked on Sentry

[NaumenkoSergiy]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/react

SDK Version

7.111.0

Framework Version

React 18.2.0

Link to Sentry event

https://tradespace-io.sentry.io/issues/4992144873/?alert_rule_id=4376506&alert_type=issue&notification_uuid=4bafaf33-aa07-425a-a7ef-d0e79f61b9dd&project=5528704&referrer=slack

SDK Setup

import * as Sentry from '@sentry/react';

Sentry.init({
    dsn: '_____________________________',
    environment: process.env.NODE_ENV,
    integrations: [Sentry.replayIntegration()],
    replaysSessionSampleRate: process.env.NODE_ENV === 'production' ? 0.1 : 1,
    replaysOnErrorSampleRate: 1.0,
    ignoreErrors: ['Non-Error promise rejection captured'],
    release: `${process.env.HEROKU_APP_NAME}-${process.env.HEROKU_RELEASE_VERSION}`,
    autoSessionTracking: true
  });

Steps to Reproduce

1. Open Product url
2. In the Javascript console I can see error like TypeError null is not an object (evaluating 'M.createdByUser.fullName')

Expected Result

I want to see the issue on Sentry, but it wasn't tracked

Actual Result

Issue was not created. Sometimes it happens, perhaps it's related that I can see Cannot read properties of undefined (reading 'value') error inside Sentry library

[AbhiPrasad]

@NaumenkoSergiy the Sentry SDK does filter some errors by default if they are ScriptErrors or similar:

sentry-javascript/packages/core/src/integrations/inboundfilters.ts

Line 10 in b61d820

/^Script error\.?$/,

If you have enabled inbound filters via the Sentry UI, the sentry server will drop errors related old browser versions or noisy browser extensions (these are usually unactionable).

https://docs.sentry.io/product/data-management-settings/filtering/

If you turn on debug: true while running the Sentry SDK, you can see if the SDK dropped any events and why. Otherwise you can go to your project stats to see how many errors are being dropped server-side.

[NaumenkoSergiy]

@AbhiPrasad thank you!

[AbhiPrasad]

Sometimes it happens, perhaps it's related that I can see Cannot read properties of undefined (reading 'value') error inside Sentry library

This seems like a bug with how we do hydration error detection in the replay sdk - we should figure out what is going on there. It seems that event.exception.values[0] can be `undefined, we should guard for it.

TypeError: Cannot read properties of undefined (reading 'value')
  at handleHydrationError(../../node_modules/src/coreHandlers/handleBeforeSendEvent.ts:24:97)
  at callback(../../node_modules/src/coreHandlers/handleBeforeSendEvent.ts:19:5)
  at <anonymous>(../../node_modules/@sentry/src/baseclient.ts:550:20)
  at Array.forEach(<anonymous>)
  at BaseClient.emit(../../node_modules/@sentry/src/baseclient.ts:550:20)
  at BaseClient.sendEvent(../../node_modules/@sentry/src/baseclient.ts:387:10)
  at onfulfilled(../../node_modules/@sentry/src/baseclient.ts:800:20)
  at Array.<anonymous>(../../node_modules/@sentry/src/syncpromise.ts:82:23)
  at <anonymous>(../../node_modules/@sentry/src/syncpromise.ts:186:18)
  at Array.forEach(<anonymous>)
  at this._executeHandlers(../../node_modules/@sentry/src/syncpromise.ts:179:20)
  at executor(../../node_modules/@sentry/src/syncpromise.ts:100:12)
  at new SyncPromise._SyncPromise(../../node_modules/@sentry/src/syncpromise.ts:61:7)
  at SyncPromise._SyncPromise.then(../../node_modules/@sentry/src/syncpromise.ts:72:12)
  at BaseClient._processEvent(../../node_modules/@sentry/src/baseclient.ts:777:20)
  at BaseClient._captureEvent(../../node_modules/@sentry/src/baseclient.ts:702:20)
  at BaseClient.captureEvent(../../node_modules/@sentry/src/baseclient.ts:229:12)
  at Scope._Scope.captureEvent(../../node_modules/@sentry/src/scope.ts:680:18)
  at Hub.captureEvent(../../node_modules/@sentry/src/hub.ts:404:21)
  at captureEvent(../../node_modules/@sentry/src/exports.ts:81:26)
  at handler(../../node_modules/src/integrations/globalhandlers.ts:120:5)
  at triggerHandlers(../../node_modules/@sentry/src/instrument/_handlers.ts:46:7)
  at GLOBAL_OBJ.onunhandledrejection(../../node_modules/@sentry/src/instrument/globalUnhandledRejection.ts:29:5)

sentry-javascript/packages/replay-internal/src/coreHandlers/handleBeforeSendEvent.ts

Lines 23 to 24 in b61d820

	function handleHydrationError(replay: ReplayContainer, event: ErrorEvent): void {
	const exceptionValue = event.exception && event.exception.values && event.exception.values[0].value;

@scttcper could you take a look at how this could happen when you get some time?