03-19-2025 13:53
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

03-19-2025 13:53
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
I've got a watch face that's compatible with the Versa 3 and a Sense, but it's been published for a few years now. I've tested it out on a brand new Sense 2, but I'm unsure how to change the Supported Devices list in the Developer Gallery App Manager. There doesn't seem to be an option.
Answered! Go to the Best Answer.

- Labels:
-
App Gallery - Clock
Accepted Solutions
03-26-2025 01:38
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

03-26-2025 01:38
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Adding "rhea" and "hera" to build targets and updating to a new version of the sdk seem to make it work. It doesn't use the Wifi bridge anymore, but a little phizallel in WSL2 and some USB voodoo magic I got it working on my Sense 2. Fitbit usually take a day to approve Watchface app updates, but it's been over a week now.
Looks like they also removed the generic music controller app (that was on the Sense1) and try to force you to use Youtube Music. So I'm probably just going to return my Sense 2 anyway as I used the music controller app like every day and will never be getting Youtube music. They shold've at least brought back Google Music.

03-19-2025 14:40
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

03-19-2025 14:40
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
I should also mention that my buildTargets is set to atlas, vulcan. I do not see a Sense2 build target on the documentation, so I'm assuming that it's vulcan for Sense and Sense 2. https://dev.fitbit.com/build/guides/multiple-devices/
When I search for my watchface in the fitbit gallery, it doesn't show up in the results. If I use the direct link to the gallery app, and open it on the fitbit app that way, Install is disabled and it has a "Not available" tag

03-19-2025 20:07
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post


03-19-2025 20:07
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
Third-party development for Sense 2 isn't supported. Some folks have managed to make progress using an abandoned beta SDK; see here and similar threads.
Gondwana Software
03-26-2025 01:38
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

03-26-2025 01:38
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Adding "rhea" and "hera" to build targets and updating to a new version of the sdk seem to make it work. It doesn't use the Wifi bridge anymore, but a little phizallel in WSL2 and some USB voodoo magic I got it working on my Sense 2. Fitbit usually take a day to approve Watchface app updates, but it's been over a week now.
Looks like they also removed the generic music controller app (that was on the Sense1) and try to force you to use Youtube Music. So I'm probably just going to return my Sense 2 anyway as I used the music controller app like every day and will never be getting Youtube music. They shold've at least brought back Google Music.

03-26-2025 10:48
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post


03-26-2025 10:48
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
HI @Slyke - if you have built a clock face for a Sense 2 the simplest way to install it on the watch is to load it into a new GAM project [with a temporary new UUID] and just install it from the private link.
That is after testing as a Sense 1 clock face in the simulator.
If you would like to explain how you did a direct installation on the Sense 2, others might be interested.
There is nothing to stop you adding the Sense 2/Versa 4 version to your original published clock face [with same UUID] by uploading to your GAM project so it can be installed on more devices.
Author | ch, passion for improvement.

