@SyncBypass Perfect, thank you!

@SuuntoPartnerTeam Hello! I’m currently developing an app and own a Suunto 5 Peak watch to test my app. I have followed the manuals and examples, and everything works as expected, except that it looks like my app crashes (or glitches) as soon as it is uploaded to my watch. After commenting out and uncommenting parts of the code, I discovered that it looks like localStorage is not available at all, so the settings cannot be loaded. My app heavily depends on being able to configure these settings. So, what am I doing wrong? Why might localStorage be unavailable inside onLoad, and how should I access it to load my app’s settings? Thank you!

@guderaber There is no way to sync images. Also no information to share regarding limitations either, I’m afraid !

@Martin-Lillepuu Exactly, and also keep the custom watchfaces (once available) for personal use without going through the bureaucratic hoops of publishing them to official store.

@Horizontal_2 I’ve used waypoints that I’ve added on the route for this purpose. This only works if you have the the route so a separate app might be a good idea anyway. I might take a look at this!

@aenzed Nice! I built a similar app, but without a Nightscout. Everything is local - Android app acts as a bridge, it talks to the pump and to the watch.

One thing that caused my grief when working with subscribed signals (HR, pace) in main.js or in onLoad is that on the simulator signals are always available. On the watch subscribed signals seem to transition from ‘undefined’ -> ‘NaN’ -> a valid number. I ended up needing to protect any use of these signals by using isFinite(), like this. // Get the index of the the active zone for a 5 zone HR gauge // v current value // zones an array of 4-values defining the 5 zones function getActiveZone(v, zones) { if (!isFinite(v)) return 0; for (var i = 1; i < zones.length; i++) { if (v < zones[i]) return i - 1; } return zones.length - 1; } Inserting systemEvent() was quite effective in pinpointing the point of failure once I understood how to do it. But I do not really get any error message, just something like this. [MR] messages are inserted by me, so I can see something happened after “G4a”, but not what the actual error was. #3251371 26.05.2026 17:44:39 : EVT UI_FRAMEWORK : JS [MR] G1 #3251372 26.05.2026 17:44:39 : EVT UI_FRAMEWORK : JS [MR] G2 #3251373 26.05.2026 17:44:39 : EVT UI_FRAMEWORK : JS [MR] G3 #3251374 26.05.2026 17:44:39 : EVT UI_FRAMEWORK : JS [MR] G4a1-not-supported #3251375 26.05.2026 17:44:39 : WRN UI_FRAMEWORK : JS I am more of a Swift or C# person used to verbose error messages and traceback. But maybe I have been spoiled.

@SuuntoPartnerTeam I had my app parat io released beginning of august 26. But since 16.8.2026, v1.3 no updates I ship are not published to the store. The Last deployed App version is v1.8 - but the App which is shipped by Suuntos App Store is still v1.3 The App Deskription will update but the app itself wont. Now I am stuck with an app I cant update anymore. Is there anything I can do, or any service i could contact? Why this matters beyond my one app: Critical bugfixes can’t be shipped in time - if a community app has a real bug, there’s currently no way to get the fix to users. Bad experience for Suunto customers - people are installing and rating outdated builds while the store listing looks fully up to date. Intransparent process for devs - no status, no version info, no feedback anywhere in Apizone about what’s actually being served or whether an update is pending, processed, or rejected. That’s tough after spending hours to elevate the Suunto eco system. p.s. the app ID is zzpara01