Browsing Issues.

[Bez2k2k]

I’m glad this thread is here. I can barely use the forum now.

 

[GrandOldTeam]

I’m glad this thread is here. I can barely use the forum now.

If you can explain why mate, it'll help people who'll be using thread to resolve.

I can see you're on iOS and Safari.

 

[Eggs]

My son looks at my problems on the GOT site on occasion when it is running slow & blames the site

….i’d have thought he’d blame Moyes

 

[Alan Whittle]

Just ignore those with iphones, mate they're just trying to be sweaty try hard coolios.

We can't all make our own phones out of balsa wood and spaghetti hoops like some people!

 

[Alan Whittle]

I'm on IOS & Safari. This started after I downloaded the latest IOS update last week.

 

[Swartzy]

I've gone from Gay tests to Korean dates, Wing Bashers and now

I am getting hounded.

 

[GrandOldTeam]

Claude AI told me the below/which I've done as a hopeful temp fix. Feedback if folk still experiencing the issue would be good.

This is a Service Worker caching issue, almost certainly related to ad scripts. Here's what's happening and how to fix it:

What's causing it​

The error FetchEvent.respondWith received an error: Returned response is null means a Service Worker (registered by ad agency/analytics scripts) is intercepting page requests on iOS Safari and returning a null response — i.e. it's trying to serve something from cache that doesn't exist, or its fetch handler is failing silently.


This is a known problem pattern with third-party ad provider Service Workers, especially after updates to their scripts that leave a stale/broken SW registered in users' browsers.

---

Fixes to try​

1. Contact ad network first Since it's their scripts registering the SW, they may have already pushed a fix or need to know. This is the most important step — describe the error and that it's iOS Safari specific.


2. Force-deregister their Service Worker via your siteAdd a small inline script to your XenForo template (e.g. PAGE_CONTAINER template) that unregisters any rogue Service Workers:

self.addEventListener('fetch', event => {
  event.respondWith(
    (async () => {
      try {
        // your existing logic
        return await fetch(event.request); // fallback
      } catch (e) {
        return fetch(event.request); // or caches.match fallback
      }
    })()
  );
});

This will silently unregister any SW on page load. It won't break anything legitimate on a XenForo forum.

 

[Bez2k2k]

If you can explain why mate, it'll help people who'll be using thread to resolve.

I can see you're on iOS and Safari.

I type and it’s super slow. But pages don’t seem to be loading properly. It keeps freezing and then says cannot load the page. No idea why.

 

[Connor]

Just finding that its really slow loading pages and even typing replies. Not an issue on any other site.

Few times last few days where I've posted a reply, it freezes, and then duplicates when posting. When I then delete the dupe post, it takes an age to go through. Same with likes, DMs, and alerts.

Can't use it on mobile, only on Macbook now.

 

[Joey66]

….i’d have thought he’d blame Moyes

He does had an argument over watching the snooker or us last night he likes attacking football......

 

[Armaghtoffee]

We've had a spike of reports of tech issues the past couple of weeks, increasing the past week or so.

It seems to be particularly troublesome on iOS devices with Safari.

I've just tested and got a "problems repeatedly with url" as reported by @Connor below.

We've made no changes at all to the forum, other than changing ad partner last month so please use this thread to report issues so I can send to their tech folk to resolve.

The operating system and browser your using and screenshots/videos particularly helpful.

If you haven't already, do try the below;

• The Service Worker on your iPhone might be trying to load an old version of a file that no longer exists on the server.
• The Fix: Go to Settings > Safari > Advanced > Website Data, find the forum URL, and swipe left to delete it. This forces Safari to register a fresh Service Worker.

View attachment 352155

I had issues for days with pages not loading properly but the workaround you posted above sorted it all this morning

 

[matty1878]

Just finding that its really slow loading pages and even typing replies. Not an issue on any other site.

Few times last few days where I've posted a reply, it freezes, and then duplicates when posting. When I then delete the dupe post, it takes an age to go through. Same with likes, DMs, and alerts.

Can't use it on mobile, only on Macbook now.

this is me it’s takes me an age to get on it’s been like this for a few days

it lets me on then either freezes or freezes if i try and navigate or stops all together or takes me back

took me ages to get on here to do this

i’m having serious withdrawals

here’s some of the stills as it well still lol
even the app is the same View attachment 352384

 

[Exeter_Gently]

I just thought the glitches where my phone being pony.

 

[GrandOldTeam]

I had issues for days with pages not loading properly but the workaround you posted above sorted it all this morning

Sounds promising.

this is me it’s takes me an age to get on it’s been like this for a few days

it lets me on then either freezes or freezes if i try and navigate or stops all together or takes me back

took me ages to get on here to do this

i’m having serious withdrawals

here’s some of the stills as it well still lol
even the app is the same View attachment 352381View attachment 352382View attachment 352383View attachment 352384

Uninstall the grand old team app on your device. It's about 6 years out of date and no longer supported.

 

[GrandOldTeam]

I'm on IOS & Safari. This started after I downloaded the latest IOS update last week.

Could be something in this, thanks.

I think it's a conflict between a third-party ad provider's code and a change in how Safari handles Service Workers in that update.

Specifically, Safari 18.4 fixed the ReadableStream cancel method not getting reliably called in Service Workers — which sounds minor, but changes to how Safari handles SW internals can expose bugs in third-party SW code that was previously working around Safari's quirks, intentionally or not.

Additionally, Safari 18.4 resolved 184 issues across various categories including CSS, JavaScript, media handling, rendering, and other areas — a large update with lots of under-the-hood WebKit changes.

There's also a broader known pattern here: Safari on iOS 16.4 and higher has a known issue where applications using Service Workers sometimes show a white page with the exact FetchEvent.respondWith received an error message — and each Safari update can shift which SW code triggers it.