2 questions regarding Settings How can a user approach my app’s seetings if i bypass the suuntoplus app? (i deploy directly…) and another settings question: on vsCode i wish to keep a setting value for the next time, so , as a test to see if it works i do: var loadSettings = function(input, output) { settings = localStorage.getObject(“appSettings”); settings.active++; if (settings == null) { settings = { maxPace: 12, timelapse: 123, active: 0 } } localStorage.setObject(“appVariables”, settings); //save } so i’m advancing ++ and saving. on vsCode indeed it works (i added debug on UI to view value), but on my watch it stays 1… ideas?

@guderaber Nice! I am surprised it works to just have a JSON copy&past over. Do you run a canvas based implementation?

Just to add, had the same issue yesterday with the route dropping temporarily when in conjunction with a guided so every new interval caused a “route lost”/“back on route” combo. Also, the watch hung on a zonesense screen, with nothing happening when buttons were pressed. Happily before I soft reset I tried the long press bottom button to escape to a menu, and then exited out, all was fine. Avoided the zonesense screen the rest of the run, but if someone else has that they may resort to soft resetting. Appreciate it’s a bit late in the cycle of watch updates to report, but any idea if these have been fixed in new SW update or are unreported? @egika @dimitrios-kanellopoulos

@SuuntoPartnerTeam Simulator seems to have a problem in getUserInterface function. This works as expected: function evaluate(input) { systemEvent('distance', input.distance); } But this breaks the simulator, and “TypeError: Cannot read properties of undefined (reading ‘distance’)” is printed to developer tool console: function getUserInterface(input) { systemEvent('distance', input.distance); return { template: 't' }; } Both work in watch.