-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Filter out known browser errors #61469
Comments
The |
I think we need a bit more examples of these kinds of errors with higher impact if we want to pursue adding a new filter. Closing for now. |
For the issue
Docs on inbound filters: https://docs.sentry.io/product/data-management-settings/filtering/#error-message |
There is a workaround that you can try as mentioned here |
Introduction
There are a number of browser errors that are known to cause problems to Developers. These errors are not actionable nor do they impact the user experience. Therefore, we believe these should be filtered automatically under a new filter called
Known Browser Errors
.__gCrWeb is undefined
We sometimes see errors like
undefined is not an object (evaluating '__gCrWeb.instantSearch.setIOSParameters')
get into Sentry's issues feed. The object__gCrWeb
get injected via script by the browser on iOS devices. Google needs to do this for some extended functionality (mostly inserting/retrieving login credentials and other form information you stored via another synced Chrome browser) which isn't provided by the native webview it's built on and can't be added to it otherwise. Since this functionality isn't required for the website to work, the recommendation is to filter out thes errors.For more info, see this Stack Overflow thread. For insights into how much this is happening in Sentry, see here.
null is not an object (evaluating 'Object.prototype.hasOwnProperty.call(o,"telephone")')
The error
null is not an object (evaluating 'Object.prototype.hasOwnProperty.call(o,"telephone")')
seems to be another browser bug. There aren't any public discussion on this (aside from this Twitter thread) but the conclusion seems to be this is a Safari specific bug in parsing certain JSON-LD content. It tries to parse the schema of an organization (which isn't even present in the schema) and fails. Doesn't seem to have any user impact and it's not actionable to the user. Weirdly enough, it also seems to only impact Next.js but there isn't a clear reason why that's true.TODO: add stack trace info
The text was updated successfully, but these errors were encountered: