refactor: Centralize ad-related error suppression in Sentry #687
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.

Fixes TANSTACK-COM-1PG. The issue was that: GamScripts'
window.onerrorhandler overwrites Sentry's, preventing proper error delegation and suppression of ad script failures.window.onerrorhandler inGam.tsxto Sentry'sbeforeSendfunction inrouter.tsx.beforeSendfunction now filters out errors originating from specific ad scripts (e.g.,fuse.js,nobid/blocking_script.js) and containing common ad-related error messages.window.onerroroverride, streamlining error handling.This fix was generated by Seer in Sentry, triggered automatically. 👁️ Run ID: 9378516
Not quite right? Click here to continue debugging with Seer.