I only noticed it when doing an update to setting.json, which would trigger that hash check exception. It looks like any new *.boot.js file would do it too though.
I just updated to 2v21.69, updated sched/alarms/locale, and forced bootloader to update (all from the development app loader).
The uncaught undefined still happens. Always after all of the console logs from booting.
I still haven't noticed any functionality issues from it (I don't use the web ide remote connection though).
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.
I only noticed it when doing an update to setting.json, which would trigger that hash check exception. It looks like any new *.boot.js file would do it too though.
I just updated to 2v21.69, updated sched/alarms/locale, and forced bootloader to update (all from the development app loader).
The uncaught undefined still happens. Always after all of the console logs from booting.
I still haven't noticed any functionality issues from it (I don't use the web ide remote connection though).