[Bug Report] Show better error message when feedback is blocked due to ad blockers

[ryan953]

I was using the Brave browser without any custom config to submit feedback and the feedback couldn't be submitted because of the built-in ad-blocking the browser has. "Shields" is their product name: https://brave.com/shields/

Repro steps:

• Download Brave and don't make any custom configs for sentry.io
• Visit pokemon-market.sentry.dev
• Open the feedback widget in the bottom-right corner
• Submit any feedback

Notice a few things around the screen:

note	screen shot
error message
Brave shields (at the browser url bar)
Blocked Network request
Network request details

I think tunneling is a very important feature to use in concert with Feedback. This is a case where no error is thrown, users see a cryptic error message a good case of a problem that feedback is designed to capture (so meta, feedback about feedback).
Also, based on the specifics of the network 'blocked' maybe we can improve the error message users see.

To use Brave, and let data flow into sentry:

• Visit brave://settings/shields/filters
• In the "Create custom filters" large text area add a line containing domain=*.sentry.io

[billyvg]

Changed the title as tunneling will work when we switchover the API endpoint to use our normal ingestion pipeline.

[bruno-garcia]

Ad-blockers breaking the ability of you to reach out to your developer is a huge problem for developers and ad-blocker users.

For reference, here's a list of places where this came up:

• POSTing to relay gets blocked by content blockers (again) sentry#25607
• ingest.sentry.io easylist/easylist#6963 (comment)
• https://community.brave.com/t/brave-standard-blocking-blocks-sentry-error-tracking/364705

[farfalk]

I think this should be at least documented on the user feedback docs until it's solved, because the feedback popup not working on my AdBlocked mobile browser during a random check on a commute (reminder to self, don't do that) gave me a heart hiccup 😅 fortunately I found this and tried again with no AdBlock, and It worked

[mydea]

@farfalk in v8 (currently out as 8.0.0-beta.3), we have an improved error message that points to ad-blockers as a possible cause (in the case we encounter a typical ad-blocker induced error). That should hopefully make this a bit clearer!

[farfalk]

@farfalk in v8 (currently out as 8.0.0-beta.3), we have an improved error message that points to ad-blockers as a possible cause (in the case we encounter a typical ad-blocker induced error). That should hopefully make this a bit clearer!

Thanks, nice to know! Is there any kind of already known non-beta release window?