Issues after Deploy

Question

Issues after Deploy

kevinhughes27 opened this issue 7 years ago · comments

Opening this issue to start tracking some issues I've seen after deploying the site. I didn't save the exception but it was related to navigating between pages. I was able to fix by refreshing, clearing application data a few times and waiting (so I am not totally sure what fixed it...). I googled for it at the time and some other people had reported it. I have since updated gatsby and all other packages so it could be fixed already. Otherwise it might only happen when the yarn bundle has changed. I'll continue to monitor and post back next time it happens.

ToDo

Hook up an exception tracker like rollbar

Kevin Hughes · Answer 1 · Sat Jan 06 2018 06:30:02 GMT+0800 (China Standard Time)

I saw it happen again. I refreshed and it worked on the next load. I checked immediately after deploy so it might be a timing thing.

Kevin Hughes · Answer 2 · Mon Jan 08 2018 14:38:03 GMT+0800 (China Standard Time)

here it is (and I have just changed my bundle)

Uncaught TypeError: Cannot read property 'call' of undefined
    at t (bootstrap 98db25e89b78efc1b299:52)
    at index.js?2281:9
    at loader.js:116
    at loader.js:97
    at index.js?2281:9
    at s (patch.js:19)
    at patch.js:40
    at window.webpackJsonp (bootstrap 98db25e89b78efc1b299:20)
    at component---src-layouts-index-js-9f2dd9c004c264ffa40a.js:1

Kevin Hughes · Answer 3 · Mon Jan 08 2018 14:38:29 GMT+0800 (China Standard Time)

normal refresh fixed it though

Kevin Hughes · Answer 4 · Wed May 02 2018 04:30:42 GMT+0800 (China Standard Time)

this was related to cloudflare caching js assets. Gatsby docs now explicitly explain not to do this. I changed to netlify which is what gatsby seems to recommend and things are fine now.