config.yml file

[bastienwirtz]

config.yml file

[bastienwirtz]

Hi @goncaloCB,

That's probably the service worker cache, it's a known issue, I'll fix it soon. In the meantime try to clear your browser cache and if necessary force the service worker update (for exemple in Chrome: Go to dev tools > Application > service worker, and click on "Update" or "Unregister"). You can also try in private navigation.

[yangkghjh]

Shift+F5, if you are using Windows.

[andrewwiebe]

Following as I would love to see this issue fixed.

[bastienwirtz]

Hi there!
@goncaloCB @andrewwiebe, just pushed a commit that remove the config file from the worker cache, it should help with this issue. Can you tell me if that's work for you?

[andrewwiebe]

For updating is it just a matter of overwriting everything and putting back our config file on top?

[andrewwiebe]

I overwrote my existing files with the update, with the exception of my config file and cleared the browser cache but am still having the issue.

Where is code change that should correct this? I just want to make sure I have the correct files my server.

[bastienwirtz]

@andrewwiebe It's there: 4b87511#diff-8a5b5909f5b3ce1a25a1c499ab30da2cL9

Truth is, your worker.js is probably cached too. That because of the lack of build system (each new release should have unique ressource URL to avoid all of that, I plan to fix that soon).

[andrewwiebe]

Nope sorry, this was my fault made a stupid mistake when copying the files. It looks like it is working!

Thanks so much.

[bastienwirtz]

Cool! Thanks for the feedback @andrewwiebe!