Blog not loading in Firefox
mathengedennis opened this issue · 2 comments
mathengedennis commented
Only the front page and about page are loading in Firefox. All the other pages are displaying an error similar to the one below.
Uncaught (in promise) Error: page resources for /blog/what-open-source-project-should-i-contribute-to not found. Not rendering React <anonymous> https://kentcdodds.com/app-86f4c733e321f3f1ba51.js:1
drinchev commented
I got the same on Safari.
[Error] Failed to load resource: the server responded with a status of 404 () (framework-efeebd7e44ddaa39810f.js.map, line 0)
[Error] Failed to load resource: the server responded with a status of 404 () (webpack-runtime-af3358f10821a7156bc6.js.map, line 0)
[Error] Failed to load resource: the server responded with a status of 404 () (component---cache-caches-gatsby-plugin-offline-app-shell-js-4e106f919af331860922.js.map, line 0)
[Error] Failed to load resource: the server responded with a status of 404 () (app-3475bbedfcba68192dfc.js.map, line 0)
[Error] Failed to load resource: the server responded with a status of 404 () (29107295-578f5c26cf508e31ab15.js.map, line 0)
[Error] Failed to load resource: the server responded with a status of 404 () (styles-821c5f1f1ffd637e866a.js.map, line 0)
[Error] Failed to load resource: the server responded with a status of 404 () (component---src-pages-index-js-738d3a1398d02c297a84.js, line 0)
[Error] Unhandled Promise Rejection: Error: page resources for / not found. Not rendering React
(anonymous function) (app-3475bbedfcba68192dfc.js:1:1683475)
promiseReactionJob
[Error] Failed to load resource: the server responded with a status of 404 () (291a736a4998dc6bb1e7dae6dfd245355445eafd-212f4d7c90adee3aa328.js, line 0)
I assume this has something to do with the Service worker. Using incognito mode did load the website.
Executing this and a reload brought back the website :
navigator.serviceWorker.getRegistrations().then(function(registrations) {
for(let registration of registrations) {
registration.unregister()
} })
kentcdodds commented
I removed the service worker and now this shouldn't be a problem anymore.