Closed garyslogan closed 4 years ago
I saw that too :( this is a great embarrassment - I tried to use the JS Date.toLocaleDateString() function, but it seems in the Fitbit SDK that doesn't use the proper local time - rather GMT. I've rewritten it now to use the proper ones, fix should be live in a week!
Ok thanks. I love the simplicity of the watch face. I've installed an alternate and will try your one again in a week or so. Gary in Oz.
On Wed, 1 Jan. 2020, 18:05 Lincoln ( ͡° ͜ʖ ͡°), notifications@github.com wrote:
I saw that too :( this is a great embarrassment - I tried to use the JS Date.toLocaleDateString() function, but it seems in the Fitbit SDK that doesn't use the proper local time - rather GMT. I've rewritten it now to use the proper ones, fix should be live in a week!
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/lincsanders/fitbit_stats_clock/issues/4?email_source=notifications&email_token=AOFFY7AMM32B7HRQLFNTCE3Q3Q6DHA5CNFSM4KBXSFL2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEH47G7A#issuecomment-570028924, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOFFY7BZV6VJ5LFBWF2ZATLQ3Q6DHANCNFSM4KBXSFLQ .
Did not update the date on 1.1.20. Day is correct but not date. I am in Australia. Is it an issue with time zone?