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
Sentry Saas (sentry.io)
@sentry/nextjs
8.44.0
Next 14.0.2
No response
sentry.client.config.js:
sentry.client.config.js
{ debug: true integrations: (integrations) => integrations.filter((integration) => integration.name != 'Dedupe'), }
Call let eventId = Sentry.captureException(error) in window.onerror.
let eventId = Sentry.captureException(error)
window.onerror
Sentry has already captured the event (in the GlobalHandlers integration?).
A second error should be sent to Sentry since Dedupe integration is removed and the eventId returned should correspond to this event.
eventId
Second error is not send and eventId cannot be found on Sentry. Sentry prints out the following debug message:
Sentry Logger [log]: Not capturing exception because it's already been captured.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/nextjs
SDK Version
8.44.0
Framework Version
Next 14.0.2
Link to Sentry event
No response
Reproduction Example/SDK Setup
sentry.client.config.js
:Steps to Reproduce
Call
let eventId = Sentry.captureException(error)
inwindow.onerror
.Sentry has already captured the event (in the GlobalHandlers integration?).
Expected Result
A second error should be sent to Sentry since Dedupe integration is removed and the
eventId
returned should correspond to this event.Actual Result
Second error is not send and
eventId
cannot be found on Sentry. Sentry prints out the following debug message:The text was updated successfully, but these errors were encountered: