Cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Some users are not able to get 12 hour clock to work

I have a clock face that supports 12 and 24 hour clock display, the code that determines which one to display is as follow:

import { preferences } from "user-settings";
const h24Mode = preferences.clockDisplay === '24h';

const hours = (
  "0" + (h24Mode ? evt.date.getHours() : convertTo12h(evt.date.getHours()))
).slice(-2);

 

It works on my Versa and Fitbit OS simulator, but a few users reported they cannot get the 12 hour clock display to work.

 

A user told me that she is using Versa as well, but using a older version of Firmware (33.1.30). Has anyone experienced the same issue? Does it have to do with the version of the firmware?

Best Answer
0 Votes
2 REPLIES 2

Are you sure it's an issue with your code, and not just the user unable to find the setting? It's a bit hidden on our website. https://www.fitbit.com/settings/profile

Best Answer
0 Votes

Yeah I am 99% sure it wasn't my code, until one user said she could get 12 hour clock working for other clock face but not my clock face. I did state it in my clock face description to promote people to go to https://www.fitbit.com/settings/profile, save and sync, but some users were still reporting problems after they doing so.

 

One possibility is that somehow they did not have the latest version of the clock face since I only added support for 12 hour clock recently.

 

At this point I can only assume it's user error, I will keep an eye on this and see I get any more reports. Thanks Jon.

Best Answer
0 Votes