On our SharePoint, we have a page with a custom-developed SPFX web part. This web part uses react-router. We developed this solution 3 years ago, and until about a month ago, it worked well. Since then, it has started to behave differently for some users. If they have no other tabs or browsers already loaded from the SharePoint site, the service worker (?) keeps adding the sw=bypass and bypassReason=abandoned parameters to the URL, resulting in an infinite reload loop. It adds the parameters, removes them, reloads the page, and then repeats the process.

It is becoming more and more frequent. It seems to be more problem in Edge than in Chrome for some reason. It happens when they have no tab or other browser already loaded from the SharePoint site, If they already have an open page , the issue is gone.

I wasn’t able to reproduce this behavior, but it happened to multiple different users.

​On our SharePoint, we have a page with a custom-developed SPFX web part. This web part uses react-router. We developed this solution 3 years ago, and until about a month ago, it worked well. Since then, it has started to behave differently for some users. If they have no other tabs or browsers already loaded from the SharePoint site, the service worker (?) keeps adding the sw=bypass and bypassReason=abandoned parameters to the URL, resulting in an infinite reload loop. It adds the parameters, removes them, reloads the page, and then repeats the process. It is becoming more and more frequent. It seems to be more problem in Edge than in Chrome for some reason. It happens when they have no tab or other browser already loaded from the SharePoint site, If they already have an open page , the issue is gone. I wasn’t able to reproduce this behavior, but it happened to multiple different users.  Read More

​