I always feel a little goofy when I solve my own problems only moments after posting about them on these forums, but apparently I have no problem anymore:
Steps to resolve:
Update and restart computer.
Try exact same thing again.
Note that this time the Banglejs2 device was NOT in the list for connections in the IDE, I had to pick web bluetooth and pair with it again.
Everything just seems to work now. Didn't restart the bangle or anything.
Huzzah!
Edit: A similar, or the same issue has arisen again, this time with the app launcher. I am going to reboot my computer again to see if it still resolves the issue.
Edit: Yes that fixed it again. The issue seems to be associated with whether or not the bangle appears "paired" already in the 'connection' dialogue. I suspect a similar thing is going on between both the web IDE and the app loader.
I notice if I navigate in chrome to : chrome://bluetooth-internals/#devices
I can see my device (DB:AD) and it sometimes shows stuff in the services column and even shows "connected" at times despite not being in the "connected" state in the app loader. Fiddling around with the "forget" and "disconnect" buttons in the chrome bluetooth management tab seemed to eventually get the app loader to work again.
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 always feel a little goofy when I solve my own problems only moments after posting about them on these forums, but apparently I have no problem anymore:
Steps to resolve:
Update and restart computer.
Try exact same thing again.
Note that this time the Banglejs2 device was NOT in the list for connections in the IDE, I had to pick web bluetooth and pair with it again.
Everything just seems to work now. Didn't restart the bangle or anything.
Huzzah!
Edit: A similar, or the same issue has arisen again, this time with the app launcher. I am going to reboot my computer again to see if it still resolves the issue.
Edit: Yes that fixed it again. The issue seems to be associated with whether or not the bangle appears "paired" already in the 'connection' dialogue. I suspect a similar thing is going on between both the web IDE and the app loader.
I notice if I navigate in chrome to : chrome://bluetooth-internals/#devices
I can see my device (DB:AD) and it sometimes shows stuff in the services column and even shows "connected" at times despite not being in the "connected" state in the app loader. Fiddling around with the "forget" and "disconnect" buttons in the chrome bluetooth management tab seemed to eventually get the app loader to work again.