Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updating script.js requires 2 refreshes to update #75

Closed
joshpowlison opened this issue Mar 8, 2019 · 2 comments
Closed

Updating script.js requires 2 refreshes to update #75

joshpowlison opened this issue Mar 8, 2019 · 2 comments

Comments

@joshpowlison
Copy link

I'm using a local XAMPP server.

I've noticed that when I update script.js and refresh the local Monogatori web page, updates aren't applied on the first refresh. It seems I need to refresh twice. I have caching disabled and don't have this issue on other pages.

Is the script cached somewhere by the engine itself? My guess is that if so, the cached version is pulled rather than the updated version, resulting in the issue.

It is also possible my local server is messing with me.

@Hyuchia
Copy link
Member

Hyuchia commented Apr 5, 2019

Hi there!

Monogatari does save everything to the cache as a part of the offline gaming feature, you can however disable this by setting the 'ServiceWorkers' option on the options.js file to false and then removing the service worker installed in your browser from the web tools.

On chrome for example you would go into dev tools > Application > Service Workers and there, find the one named service-worker.js and click on Unregister.

After that, you won't need to refresh your browser twice but it is recommended that you enable it up again when releasing it.

@Hyuchia
Copy link
Member

Hyuchia commented Feb 9, 2020

We're closing this now as this is expected behaviour and is fixed by either disabling the service workers during development or changing the worker version to force a re-cache.

@Hyuchia Hyuchia closed this as completed Feb 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants