Thanks for your response, I had indeed looked at this post.
Following both suggestion in the article, I have temporarily remove the service worker on the application. But I can still reproduce intermittently the issue from there. The issue is not reproducible consistently.
When I download the build application on Netlify, I cannot see any issues and the files are all in place.
However I’m curious about some 301 redirects from disk cache that fails to give a valide response type. See below on the screenshot of the Gatsby webpack runtime js file requst.
@johnedvard mentioned “We managed to use CI, with automated builds from bitbucket (instead of dragging our dist folder into Netlify), and the the same problem has not occurred (yet). Maybe Netlify is doing something important when they build the application instead of us.”
However I am currently unable to use netlify CI due to specific env variable setup to build the application. I am building the application locally, then pushing the entire app. (something I would like to improve in the future).
Can you confirm if using drag and drop might cause the issue I’m experiencing ?
FYI I had to added as a temporary fix a “no-cache” tag in the headers of all my request. The issue was affecting the production site. The “no-cache” tag removed the issue. This is obviously not ideal and would need to be removed soon.
Let me know if you need more information about the issue raised.
Hi, it looks like you cross posted on another thread. It does look to be the same issue. I’ve posted a response on that thread but wanted to circle back here so anyone looking at this thread knows where to look.