The try block calling the user code:
|
? replayOptions.beforeAddRecordingEvent(event) |
Leads to the catch block that records internal SDK error:
|
client.recordDroppedEvent('internal_sdk_error', 'replay'); |
This can make debugging a high number of internal sdk errors
Some ideas:
We could add the invocation to a different try/catch block. Drop the event in case of an error.
Alternatively we could record a breadcrumb:
https://github.com/getsentry/sentry-dotnet/blob/2bee53c4a2ae9bcc72a7f3f72f9675b064849cfb/src/Sentry/SentryClient.cs#L352-L375
The try block calling the user code:
sentry-javascript/packages/replay/src/util/addEvent.ts
Line 51 in 2b4121f
Leads to the catch block that records internal SDK error:
sentry-javascript/packages/replay/src/util/addEvent.ts
Line 68 in 2b4121f
This can make debugging a high number of internal sdk errors
Some ideas:
We could add the invocation to a different try/catch block. Drop the event in case of an error.
Alternatively we could record a breadcrumb:
https://github.com/getsentry/sentry-dotnet/blob/2bee53c4a2ae9bcc72a7f3f72f9675b064849cfb/src/Sentry/SentryClient.cs#L352-L375