Clock Error Go to the Fitbit mobile app and try another clock error

[swla]

Hello,

Has anyone else been having users complaining of this error? I haven't managed to replicate it in the few months I have been using my Fitbit to catch the error.

Any suggestions as to what might be the cause?

Thanks

[Drifty26]

I've occasionally seen that error when I've installed a new version of my app, but only on the first launch.

My guess was that when a new version was installed the prior version was not shut down correctly, but that is only a guess.

I've never seen it once an app has been run successfully.

John

[Gondwana]

It could be occurring if the clockface is too slow to start. In theory, it's only got ten seconds to get going, but it can take about that long for the operating system to create an executable bundle for a complicated clockface, which doesn't leave long for your code to run its startup routines.

This is hard to investigate, but you might get some clues by converting it to an app for testing purposes, and note how long it takes to wake up after a clean installation on a real device.

[swla]

Thanks for the suggestion. I've have asked the users that have seen the error what they were doing at the time and am awaiting a response. 

My initial impression was they were using the clock face for a while and it randomly displayed this error.

[djdoornink]

I'm experiencing the same behavior with my clock face app. I've never seen this on the simulator making quite hard to debug. But, since I see it almost every morning when I wake up, I've noticed a pattern that might make sense to someone more experienced with JavaScript and/or the Fitbit OS in general.

Here is what I've observed:

1. It only happens at night while I'm sleeping. I've never seen it happen seen it during the day. I do wear my Versa at night. 

2. The only debugging feedback I get is from the Logs left on the Fitbit App on my iPhone and the only two messages that appear are :

AppLifecycleMessage:launchApp and AppLifecycleMessage:terminateApp

3. During normal operation during the day I will see a "AppLifecycleMessage:terminateApp" when I launch another app and then a "AppLifecycleMessage:launchApp" when I close the app which restarts the clock face.

4.The typical night pattern begins after 12:00AM (which leads me to suspect there is something with the time and day wrap-around that triggers it in my app). Last night started at 2 seconds after midnight.

AppLifecycleMessage:terminateApp  12:00:02

AppLifecycleMessage:launchApp 12:00:02

AppLifecycleMessage:terminateApp 12:00:03

AppLifecycleMessage:launchApp 12:00:03

AppLifecycleMessage:terminateApp 12:00:04

AppLifecycleMessage:launchApp 12:00:04

AppLifecycleMessage:terminateApp 12:00:04

AppLifecycleMessage:launchApp 12:00:04

AppLifecycleMessage:terminateApp 12:00:05

AppLifecycleMessage:launchApp 12:14:02

AppLifecycleMessage:terminateApp 12:14:03

AppLifecycleMessage:launchApp 12:14:03

AppLifecycleMessage:terminateApp 12:14:04

AppLifecycleMessage:launchApp 12:14:04

AppLifecycleMessage:terminateApp 12:14:04

AppLifecycleMessage:launchApp 12:14:04

AppLifecycleMessage:terminateApp 12:14:05

AppLifecycleMessage:launchApp 12:30:02

AppLifecycleMessage:terminateApp 12:30:03

AppLifecycleMessage:launchApp 12:30:03

AppLifecycleMessage:terminateApp 12:30:04

AppLifecycleMessage:launchApp 12:30:04

AppLifecycleMessage:terminateApp 12:30:04

AppLifecycleMessage:launchApp 12:30:04

AppLifecycleMessage:terminateApp 12:30:05

And this pattern of 4 sets of ‘launchApp, terminateApp’ occurring every 16 minutes continued until I got up at about 8:00AM.

Is there anyone out there that can make sense of this? I'd love to hear any theories.

Cheers,

Doug

[JonFitbit]

---

@djdoornink wrote:

Is there anyone out there that can make sense of this? I'd love to hear any theories.

---

Is this only happening with your project? Can you share the source on Github?

[djdoornink]

I'd be happy to share this on Github but I've never used Github before so I could use some help there. Could you point me to some instructions?

[JonFitbit]

You could share the code via a Dropbox or Google Drive link if that's easier.

If you want to learn about Git and Github, here's a tutorial https://product.hubspot.com/blog/git-and-github-tutorial-for-beginners

[djdoornink]

For the sake of expediency I’ll share the project via Google Drive. Here is the link.

https://drive.google.com/file/d/1TLKkXuTgEFqgFQMUyJAz2jKl10zqUBrz/view?usp=sharing

Full Disclosure -  I’m just learning JavaScript and this is my first Fitbit app. Here is a short description of 

the clock face functionality.

The clock face displays the Date and Time.

Beneath the Time there are 4 horizontal progress bars that change color to green when goal is met.

250 Hourly Steps progress bar

Daily Stairs to Goal progress bar

Daily Steps to Goal Progress bar

Current Pulse which changes color according to the current heart rate zone.

There are two invisible buttons: 

Upper left quarter of the screen will toggle heart rate on and off

Upper right quarter fo the screen will toggle total daily steps display on and off.

The app works fine and behaves as I expect during the day but generates the strange log messages at night after 12:00AM and the Clock Error display in the morning when I wake up.

Thanks for the help,

Doug

[swla]

@JonFitbit Any thoughts about why this happens yet? I still haven't come across anything yet, but it is still happening to users of my clock face. I have never personally experienced this error on my own device so I can't debug very well.

On the initial side load my clock face takes about 9 seconds to load. After the initial load then all subsequent loads (like returning from an app, the settings, or "today") take 1s or less. Also, the fact that this happens overnight makes me think it is less of a launching issue and possibly something else occurring.

Of note, I am using the ASAP code in my project with v1.0.6. I am not sure if @djdoornink was using this as well... I have an updated version pending with v1.2.1 so I do not know if this will solve the problem.