Bug Report - Service Worker error loading route /sites/[username]/metrics/rum on app.netlify.com

Support
1

Gday Netlify Engineers,

I tried to submit this using the form at bugform.netlify.app, but I got a bunch of CORS/CORB errors.

Sorry if this isn’t the correct place to send a bug report, just let me know for next time.

Anyway, I did copy the format of that bug report form below.

This is not a huge issue, just a bit weird.

Cheers!

Bob.

===================================================

Name: Bob
Email: gpb@monkeyisland.com.au

Phone: [redacted]
Browser: Version 128.0.6613.189 (Official Build) (64-bit)
OS: Windows 10 22H2

Severity of the bug: Minor S4
Select the platform where showed up: Admin Platform (app.netlify.com)
Screenshot: Attached (below)
Description:

When navigating using just the “URL bar” and pressing enter or “Open in New Tab”, i.e. not clicking on any links to navigate, the following route doesn’t load:

I assumed you guys were loading this page with a virtual DOM / js-router thing and forgot to hook up an external route to load.

But when I looked in my console it was not a normal 404, and there is actually an external URL handler for that route set up…

It looks like it’s actually the service worker going a bit bonkers. Just only for that route “/metrics/rum” when navigating using the URL bar.

I unregistered the service worker and it went back to working externally like normal… wacky!

¯_(ツ)_/¯

I attached a screenshot (please excuse my awful MS Paint skills). I can send you the full .har capture of my session if you want.

I think it traced back to the service worker’s “respondWith” function but yeh, that’s all I got.

Cheers lads!

===================================================

2024-12-04 02_34_58-
2024-12-04 02_34_58-1883×1619 438 KB

2

That’s not a Netlify-owned site, so you were essentially reporting this to some random user.

As far as the report is concerned, the page loads fine. I see this:

image
image1954×736 66.6 KB

I didn’t have to do anything with service workers. Looks like something went wrong onn your specific device.

3

Gday @hrishikesh

Thanks for looking into it, that would probably explain why that bug report site didn’t work! heh.

I tried again with Firefox, new Chrome version and Chrome canary and I think you might be right, it worked fine with all those, just not my current (slightly older) version of chrome.

My bad!

Thanks for checking it out anyway, I’ll try and write a better report next time.

Cheers

Bob