help menu

Join us on the Community Forums!

  • Community Guidelines

    The Fitbit Community is a gathering place for real people who wish to exchange ideas, solutions, tips, techniques, and insight about the Fitbit products and services they love. By joining our Community, you agree to uphold these guidelines, so please take a moment to look them over.

  • Learn the Basics

    Check out our Frequently Asked Questions page for information on Community features, and tips to make the most of your time here.

  • Join the Community!

    Join an existing conversation, or start a new thread to ask your question. Creating your account is completely free, and takes about a minute.

Not finding your answer on the Community Forums?

Cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Bug report: date in first tick after clock granularity change is incorrect

‎05-16-2020 09:48 - edited ‎05-17-2020 03:14

‎05-16-2020 09:48 - edited ‎05-17-2020 03:14

Expected

The first tick when changing clock.granularity from minutes to seconds fires on next second and reports the correct seconds value in event.date.getSeconds().

 

Actual

The first tick event event.date.getSeconds() reports 0. The second tick event reports the actual, correct seconds.

 

Confirmed in Fitbit OS Simulator and Fitbit Versa 2 version 70.7.21. Bug only present when Always On Display is not enabled.

 

See video and example code that prints the seconds value via console.log and updates the text on screen at https://github.com/jeremiahlee/fitbit-first-tick-seconds-bug

Best Answer
Labels:
0 Votes
0 REPLIES 0