10-16-2019 09:14
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

10-16-2019 09:14
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Can we please get a date for when Fitbit studio will be available for the Versa 2?
As it is today, you have marked old Versa apps as suitable for Versa 2 even if not fully working. That creates a lot of noise: Emails from users requesting support. The combination of half-working apps and unavailable tools to fix those apps is extremely frustrating!

10-21-2019 01:45
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post


10-21-2019 01:45
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
It's coming, hang in there.

06-09-2020 19:52
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

06-09-2020 19:52
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
I created a clock face app in FitBit Studio but it does not show up in Developer Menu under sideloaded app so I cannot install it on my Versa 2. FB OS Simulator is synced and shows device bridge is connected to a debugger but says companion bridge is waiting for debugger? Any suggestions? I called support and they told me to contact the clock face developer after I told them I created the clock face in FB Studio. 🤣

06-09-2020 20:01
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post


06-09-2020 20:01
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Companion bridge would be referring to the connection between Studio and your phone (or whatever is running the Fitbit mobile app). Make sure the 'Developer Bridge' is 'Connected' within the Fitbit app on your phone.
Sometimes the list of sideloaded apps doesn't play nicely. Refreshing it (by swiping down?) sometimes helps.
Gondwana Software

06-09-2020 20:26
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

06-09-2020 20:26
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Hello dmllewellyn,
I think we have all had to work through these issues on our first Fitbit efforts, 😬
You may want to try turning off the simulator to force the load to the phone/Versa 2. The simulator tends to confuse the issue.
Also, make sure watch and phone both have the developer bridge turned on. You will need to check the watch periodically, as the physical hardware tends to disconnect the bridge on its own. They will show up as menu options in the Fitbit studio when they have successfully connected.
I also occasionally have had to restart the Fitbit app, and sometimes the phone to get the developer mode to work.
Regards,

06-10-2020 05:41
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

06-10-2020 05:41
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
In addition,
One thing I have noticed is that the developer bridge gets extremely fussy when you have two developer tabs or windows open. It almost always causes weird connection issues. I wonder if having the emulator open while trying to connect to hardware could also be problematic.

