-
• #2
(message with potential workaround deleted - that trick worked just until the next reconnect)
-
• #3
I might have found a solution:
- at first, connect using the Web IDE
- then, in another window, open the App Loader and connect (the Web IDE will show you any responses from the watch)
- upgrade any outdated apps (e.g., Settings, Bootloader etc.) and/or delete an old/install a new application
From then on, everything seems to work fine again - but don't ask me why!
- at first, connect using the Web IDE
-
• #4
Glad you got it working. It could be caused by a clock face/similar taking far too long to render? Was it something that you'd written yourself, or is the watch standard?
The IDE has some code to recover from having hit debug mode though (which you get from a Ctrl-C if you're in a loop that is taking a long time to finish) and that could be ported to the app loader if this turns out to be a problem for many people?
-
• #5
Unfortunately, I can't remember any more - at least, I got it working again, that's what counts!
I just updated my Bangle.js 2 to firmware 2v11 - but now, the app loader no longer allows me to do anything. Since the error messages ("toasts") disappear after a few seconds (could that be changed, please!), I had to look into the browser debug console for more information. Here is what I found there:
Basically, the watch claims to be "in debug mode" which is why the App Loader does not get the expected JSON.
If I connect to the watch using the Web IDE and then type "help" into its left side, I get the response
"help" is not defined
:I already reset my smartwatch several times, without any luck.