I did make some mistakes, but without any impact (wrong signature for getUserInterface, …) The actual real reason I did get the “Maximum SuuntoPlus Apps reached” is because I was using regex in main.js … This is not documented, so warning for all the other devs: do not use regex as this will work with the simulator but not with your watch!

@SyncBypass I love this [image: 1777722759138-1000024454.png]

Your watchface looks nice. It is simple and easy to read. Can you modify it to have 3 bottom data fields, same as top row? Could you please share your code?

Agree, btw, based on the feedback/rating a user provide to my app, users also want that Your app Anchor Alarm has received a feedback: Rating: 3 Comment: Should be available outside a sport function also. And to be honest, it’s a bit of a shame to get 3 starts of 5, because the “issue” is out of my control, I do not have ability to fix it.

@isazi the sdk is so easy to work with that I wouldn’t be surprised that this is the case. I’m so happy with the watch itself and the general software experience so this is essentially the last puzzle that allows getting rid of other platforms and consolidating everything sports/longevity related around my suunto

@Unpaired8373 Does this happen with a fresh application from Create App or only with the one you’re working on? Our team member with an M2 Macbook reported not being able to reproduce this error.

Just registered to let you know that I believe this is an issue with how SDS (the server interfacing w/ the IDE extension and the watch’s protocols ?) is spawned by the Suuntoplus Editor. I’m facing the exact same issue, only on a macbook w/ an M4 Pro chip instead of an M3 Max one. Running the following command starts SDS, which after a few seconds picks up the watch and starts the pairing process. SDS_MACOS_BLE_SCAN=1 ~/.vscode/extensions/suunto.suuntoplus-editor-1.42.0/node_modules/@suunto-internal/sds-as/macos/SDSApplicationServer.bin 9801 As a workaround, I tweaked my local version of Suuntoplus Editor to prevent it from starting SDS (via a coding agent, which worked surprisingly well from the first try), and I’m starting it manually in a terminal. The relevant file is ~/.vscode/extensions/suunto.suuntoplus-editor-1.42.0/node_modules/@suunto-internal/sds-as/dist/sds.js The watch is then displayed in VSC, and could be loaded with my app without any issue. [image: 1774720045117-0695f3ac-b672-40ca-87a4-3b948013860b-image.png] I hope that this info will let you debug and patch the Suuntoplus Editor As a side note, I was quite happy to see this editor being available free of charge and without any signup process