01-25-2019 10:07 - edited 01-26-2019 06:19
01-25-2019 10:07 - edited 01-26-2019 06:19
Hey there,
I'm well aware that one typically develops applications primarily on the Fitbit OS Simulator, but there are some cases which seem to be inconsistent between the watch and the simulator, so I recently moved over to debugging on the watch occasionally to make sure everything is working, etc.
My versa watch is really finicky in terms of when it decides to disconnect from the debugger. It doesn't seem to always matter if I keep the screen on or not - sometimes it just disconnects while I'm interacting with my application and it's not obvious until I need to build & install. Are there specific conditions under which the watch and phone disconnect from the debugger?
Thanks & regards
01-28-2019 15:32
01-28-2019 15:32
Are you using Studio or the command line tools?
The device will disconnect if there's extended inactivity, or if the battery level drops below 25%.
01-28-2019 17:57
01-28-2019 17:57
I'm using the CLI tools at the moment but when I was using the Studio I would see the same behavior.