As I was reading the latest Gatsby gazette, I clicked this link to the "Gatsby for apps" blog post, but the page remained white. It loaded after reopening it again.
It looks like a similar error as I reported previously, but Kyle said that one should have been fixed in v2.
Don't know how to reproduce.
The page should have loaded.
Page was entirely blank. Console showed:
Unhandled promise rejection Error: "Loading chunk 43 failed.
(error: https://www.gatsbyjs.org/43-6892247c8fc728767d9f.js)"
n https://www.gatsbyjs.org/webpack-runtime-f4da6aa995ca964afdff.js:1:6825
L/</t< https://www.gatsbyjs.org/app-e85d14a7fe2197fb94f6.js:1:31219
e.exports https://www.gatsbyjs.org/app-e85d14a7fe2197fb94f6.js:1:69811
L/< https://www.gatsbyjs.org/app-e85d14a7fe2197fb94f6.js:1:31096
e.exports https://www.gatsbyjs.org/app-e85d14a7fe2197fb94f6.js:1:67993
<anonymous> https://www.gatsbyjs.org/app-e85d14a7fe2197fb94f6.js:1:45186
y https://www.gatsbyjs.org/app-e85d14a7fe2197fb94f6.js:1:45044
b https://www.gatsbyjs.org/app-e85d14a7fe2197fb94f6.js:1:45064

Firefox 63.0.1 (64-bit), macOS 10.14.1.
I faced this issue yesterday while opening gatsby blog in my mobile chrome browser. The page finished loading, but it was blank.
After reloading, it loaded properly.
It can't find a js file, that is expected to be there. Probably a serviceworker issue?
Working allright on my end. Tried it on chrome desktop(normal and incognito), firefox(normal and incognito) and edge. Same result, loads ok. That used to happen to me when visiting the site after gatsby v2 was implemented. And the site was migrated to that version. Had to reload 2 to 3 times to get the actual content. After a bit of detective work it looked like it was related to the service worker not storing the file
Hey there, I think this should be fixed once #9907 is merged!
Most helpful comment
Hey there, I think this should be fixed once #9907 is merged!