10-25-2020 18:47 - edited 10-25-2020 19:02
10-25-2020 18:47 - edited 10-25-2020 19:02
Hi,
I recently made a clockface with Fitbit studio for my dad's Sense. I am able to run it perfectly fine on the Simulator and on his watch via the developer bridge (although running the clockface this way seems to be more of a preview and we can still see the previously loaded clockface on his watch). However, when I published it and asked my dad to download it via private link, the clockface installs as a black screen.
Any help is much appreciated!
10-26-2020 10:15
10-26-2020 10:15
Just a guess...did you set the permissions correctly?
10-26-2020 15:47
10-26-2020 15:47
Yes, all the permissions are set correctly!
Just to double check, I unchecked all the permissions in `package.json` and ran it in the simulator which does not give a black screen (it can still show my icons and the battery percentage). So I think this means that if permissions were the issue, at least part of my clock face would show up correctly.
11-02-2020 08:43
11-02-2020 08:43
Normally this is because you've used an image which is much larger than the screen dimensions.
11-02-2020 17:52
11-02-2020 17:52
Hmm, I don't think that's it. My images are all smaller than the screen
11-02-2020 18:05
11-02-2020 18:05
Check image formats. For example, not all types of JPG are supported on the watch.
The watch can also struggle to resize or rotate large images, and can crop images that are partially off-screen.
Can you provide more details about "running the clockface this way seems to be more of a preview and we can still see the previously loaded clockface on his watch"? Under what circumstances are you still seeing a previous clockface?
11-02-2020 18:50
11-02-2020 18:50
Ah I see, all my images are PNG images and are more or less the size that I want them to be on the watch.
If I run my clockface over the developer bridge onto my father's watch, we can still swipe left to go back to the previously loaded clockface (the default Fitbit one). I found this kind of strange because when I load clockfaces onto my Versa 2 via the developer bridge, they are able to load and work like a proper clockface without problem, but on the Sense it seems to just be a "preview" of some sort?
11-02-2020 19:03
11-02-2020 19:03
Thanks for the explanation. I haven't noticed that behaviour in Versa 3 (which should be equivalent to sense).
If you're not building a SDK5-specific version of your clockface for the sense, the sense will be trying to run it in 'compatibility mode'. That introduces a new set of possible issues (although I'd expect something to be visible). If it's not too difficult, see if you can create a SDK5 version.