09-06-2016 11:35
09-06-2016 11:35
Three images are attached. I started walking at 1:54 PM with 5868 steps. At 2:00 PM, I had 6395 steps, yet the 250 steps per hour graphic shows no change...including the larger grey dot to indicate that we're now on the 2 o'clock hour. The third image shows that even 7 minutes later, the app is still connected to the tracker and it's counting steps, but it's not recognizing the achievement in the 250 steps per hours (nor that it is at the 2 o'clock hour). The only thing that fixes this is to "force quit" the app and restart it...then the graphic shows correctly.
Sometimes you want to meet this goal but quickly need to return back to work. Not having an accurate reflection of when I've achieved this goal makes it all the more difficult to know when I can resume work.
09-06-2016 14:13
09-06-2016 14:13
@geehaad I'd recommend updating to the latest version of the Fitbit iOS App, version 2.26.1. Click here to be redirected to the iOS App Store.
This updated version of the App should resolve the problem, but keep me posted either way.
09-07-2016 11:23
09-07-2016 11:23
Updated as you suggested and it still doesn't work (see images below).
I believe there is other stuff being taken into consideration in terms of meeting this metric, possibly including the validation of Heart Rate. I believe this because the heart rate monitor on Tracker #2 (I'm on #3 now) mostly didn't work, so I often would not get credit for the 250+ steps, even though the number of steps had increased way more than 250 in the hour. In any case, clearly it is not a simple addition/subtraction formula that validates this metric, and it really needs to be that simple.
09-19-2016 07:32 - edited 09-19-2016 07:32
09-19-2016 07:32 - edited 09-19-2016 07:32
It's great to have you here @geehaad! Thanks for the screen shots provided, we've released a new update, 2.27 (587) on 9/16/2016.
To see what version of the Fitbit app is installed on your device:
To update the Fitbit app to a newer version:
Also, I'd recommend doing the following:
Let me know if this works!
Was my post helpful? Give it a thumbs up to show your appreciation! Of course, if this was the answer you were looking for, don't forget to make it the Best Answer! Als...
09-27-2016 11:18
09-27-2016 11:18
Have you attempted to duplicate this problem but cannot? As per my original post, force-quitting works. Why would that be necessary when the app correctly reflects the increased value for Steps Taken?
It is still happening on the latest version, and it would be nice if you would please stop asking your users to update to the latest version unless you have some *reasonable* suspicion that the stated problem has been addressed by a more-recent version of the software. It's entirely unnecessary to do otherwise.
Latest screenshots: