We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SaaS (https://sentry.io/)
When capturing an exception manually, the eventHint.originalException is not being set before triggering the beforeSend function.
client.captureException(exception);
captureException signature is "captureException(exception, hint, scope)"
this will internally call
this._captureEvent(event, hint, scope) -> this._processEvent(event, hint, scope)
and _processEvent calls the processBeforeSend without modifying hint:
processBeforeSend(options, prepared, hint)
Hint to include the original exception before triggering beforeSend
The beforeSend function has no access to the originalException.
Unknown
No response
JS SDK Version: 7.119.2
The text was updated successfully, but these errors were encountered:
Assigning to @getsentry/support for routing ⏲️
Sorry, something went wrong.
Hi @dcarabott which SDK package and version are you using?
Hi @InterstellarStella, we're using the JS SDK through the CDN link. Version right now is 7.119.2.
7.119.2
No branches or pull requests
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
When capturing an exception manually, the eventHint.originalException is not being set before triggering the beforeSend function.
captureException signature is "captureException(exception, hint, scope)"
this will internally call
and _processEvent calls the processBeforeSend without modifying hint:
Expected Result
Hint to include the original exception before triggering beforeSend
Actual Result
The beforeSend function has no access to the originalException.
Product Area
Unknown
Link
No response
DSN
No response
Version
JS SDK Version: 7.119.2
The text was updated successfully, but these errors were encountered: