[Bug]: Brave browser blocks SDK script

[promisetochi]

What happened?

Brave browser blocks onesignal scripts. Is it okay to rename onesignal script files and serve them directly on the host applications domain?

What browsers are you seeing the problem on?

Brave

What operating system are you running?

MacOS Sonoma

Steps to reproduce?

1. Install
2. Call OneSignal.init() in a react hook
3. Browser blocks https://cdn.onesignal.com/sdks/web/v16/OneSignalSDK.page.js

What did you expect to happen?

Expected script to lead and evaluate

Relevant log output

GET https://cdn.onesignal.com/sdks/web/v16/OneSignalSDK.page.js net::ERR_BLOCKED_BY_CLIENT

[jkasten2]

@promisetochi This is a known issue with both v15 and v16 of the OneSIgnal SDK with Brave. It seems the Brave browser is blocking the OneSignal Service Worker import, even when shields are down. This seems like a bug, as shields down should let things through so I recommend reporting this issue to them.

See this comment for more details: https://github.com/OneSignal/OneSignal-Website-SDK/issues/526#issuecomment-978354383

[promisetochi]

@jkasten2 thanks for the response.

It seems like an issue that OneSignal should be concerned about though. Browsers are basically (intentionally or unintentionally) defeating the purpose of the product.

iOS Safari also seems to block OneSignal scripts as well and this is a setting that seems to be on by default. Mixpanel will be an easy fix for me by renaming and moving the js file to our domain, not sure if that's possible with OneSignal. If there are any guides on self-hosting, could you please point to it?

[AndreMiras]

Would it be helping if the OneSignalSDKWorker.js script was embed with react-onesignal and served from the same domain?