You are reading a single comment by @Raik and its replies.
Click here to read the full conversation.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
@Raik
Hi there,
so I forked my own app loader to create new apps. What I'm having difficulty with is refreshing the app loader in Chrome after pushing changes into the repository.
Chrome often still shows old versions of apps (e.g. version numbers and changelog text) and only after a clearing all data on Chrome and restarting Chrome itself do I see the changes. This is kind of annoying. Is there any other way to tell the app loader to reload all files from scratch or is this indeed a Chrome caching issue?
Anyone else experiences this?
EDIT: So right know I can't even trigger an update of the app loader in Chrome. Deleted all caches and cookies and what not, but still I don't see the updated Changelog and if I re-upload the app it is still the old version, not the updated one.