-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
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: CustomEvent
captured as promise rejection
#1913
Comments
CustomEvent
captured as promise rejection
I'm having trouble reproducing the error, so I'm going to unassign myself. I'll post some notes below:
|
The first Sentry event happened on Aug 1, 2023 10:51:32 PDT. #1865 (small styling change) and #1849 (update Nextjs to 13.4.12) were merged within an hour before that event. Several unknown promise rejections stopped happening around Aug 1. This event could be a new bucket for those kinds of errors due to the framework update. |
Probably related to getsentry/sentry-javascript#424 You can reproduce errors like this and have them show up in Sentry by doing something like the following in the browser console
I'm not familiar with your project but for issues I've seen related to this it's due to browser extensions in user's browsers. |
Thanks for the link @jensbodal! That's a clever way to trigger Sentry events from the console, TIL. We'll see if anything changes when we upgrade to Next.js 14, but I vote we start filtering out these errors since they chip away at our Sentry budget and they don't seem to indicate a fixable problem. |
The problem seems to be it's not possible to filter them out in all cases: getsentry/sentry-javascript#9589 |
We may not be able to do anything about this, but let's figure that out. It started recently, maybe we can stop it?
Sentry Issue: REACT-COMMERCE-30M
The text was updated successfully, but these errors were encountered: