Potential CSP issue with Safari only devices and Google Tag Manager

I am running into an issue with a eCommerce website that appears to work fine on desktop and Android browsers, however when loading the site on a Apple based device with Safari it is breaking some other javascript functionality that the page uses (e.g such as jQuery performing a page-reload on changing an option from a ‘Sort By’ dropdown menu.

I don’t have an actual iOS phone to test but have put the website in question into an iOS simulator running an ‘iPhone 16’ with Safari and enabled debugging so I can view the console errors directly on my Mac Mini. Note – these issues ONLY happen on iOS devices with Safari and not Android (also no issues with regular desktop browsers).

When loading a particular category page I am getting the following error within the simulator console (note I have changed the site url for security reasons)

Refused to load https://www.googletagmanager.com/static/service_worker/53b0/sw_iframe.html?origin=https%3A%2F%2Fwww.mysite.com  because it does not appear in the frame-src directive of the Content Security Policy.
Refused to load https://metrics.mysite.com/_/service_worker/53b0/sw_iframe.html?origin=https%3A%2F%2Fwww.mysite.com&1p=1 because it does not appear in the frame-src directive of the Content Security Policy.

Would this require me to alter some Content Security Policy (CSP) settings to take this into account properly? I am not too familiar with CSP so any advice is welcomed, but I am reading that the Safari browser ITP (Intelligent Tracking Prevention) is much more aggressive than Android browsers and this can affect how service workers and tracking-related iframes are loaded which maybe effecting the Google Tag Manager in this instance.

So an example of the flow would be :

  • User goes to xxx page and selects ‘Sort by lowest price’ from the dropdown
  • This performs a page reload with the lowest price product
  • On safari devices this breaks so using the dropdown will not actually perform a page reload

I am debugging this using an iOS simulator on my mac, with the following versions if this helps:
Running MacOS 15.3.2
Xcode 16.2
Simulator 16.0 (1038)
Safari browser