RESOLVED: Distance travelled does not match distance logged

[DerrickS]

Fitbit Update 03/09/17

Hi everyone -- Some good news to share! This issue should now be resolved!

If you were previously experiencing this issue on iOS, please try it again as our team has pushed out a fix. Feel free to give me some feedback about your post-fix experience. Thank you for your patience as we worked to get you all back on track.

---

Fitbit Update 2/28/17
It was recently brought to our attention that some iOS users are experiencing their mile splits for GPS workouts don’t add up to the total distance of their workout. Our team is aware of this issue and is currently working towards a fix.

[tracey2]

At the risk of jinxing it, I logged a walk this afternoon and it appears to have synced distance and pace correctly (for the first time since 2/22):

Not sure yet if the issue is truly fixed, or if this bit of accuracy is a fluke, but I'll take it.

[majbugman]

@SunsetRunner

I don't know how you figured that out but that sounds like a good work around until a fix is done. Thanks!

I am annoyed also, obviously, that we have to do that many back flips to get pretty basic workout data.

[Ty2417]

Every morning when I do my 3 mile workout, it tracks the 3 miles and then as soon as I hit "finish" it saws I only did 0.51 miles. It has done this every day since 2/21! 

[Pjd1300]

@tracey2 you got lucky and/or experienced an anomaly (like you said: a fluke).  I usually log 2 to 3 "workouts" A DAY, but for the past week only 2 workouts have logged a distance even close (ONE was right on) to the milage that I actually put in.  It would, however, be nice if what you experienced would continue 

[SunsetRunner]

@DerrickS - Finally we have a reply from a mod! Thank you - can you make this thread a pinned thread please ! 

[EllieRoss]

I am also having this issue - ran 18km on Saturday 25, but my fitbit logged 9km (Spilt km are correct)

Please sort this out ASAP - I am running the Surrey half in a few weeks and wont this fixed!!!!!!! 

[Jueday]

Yep this happening to me too, 

Using iPhone 6s  iOS 10.2.1 and using Fitbit app for gps!

totally gutted when it recorded 11k as 0.5k  

[sidrich]

I am having the exact same problem using the Flex and the Fitbit app on iPhone 6 using the Run feature. Distance is accurate throughout the run, the splits are fine, and RIGHT BEFORE I press the button to end the run, the total distance and the average split pace are accurate. But as soon as I hit that button, the distance drops (a run of 3.1 miles becomes 0.55 miles), the total time is the same, so the average pace is adjusted. 

My steps are still counted correctly, so I think the Flex is working fine, it seems to be a problem with the iPhone app suddenly recalculating total distance run upon the completion of a run. I wonder if it is for some reason just calculating the distance between start and finish locations and using that as total distance?

[Digger.2009]

Same as you using the recent updates etc. ugh! This really needs to be fixed

[ELasater]

1. What type of iOS device are you using?  - iPhone 5

2. What iOS version is your device running (ie iOS 10.2, iOS 8 ,etc)? iOS 10.2.1

3. Were you using the Apps GPS, Surge's built-in GPS, or Charge 2/Blaze's Connected GPS to track your workout?  Fitbit App's GPS 

4. Does force quitting and reopening the App help? No.

I have been using the app to track my walks and recently noticed that the summary at the top is different than the split times and mileage. Manually doing the math using the split distance and times results in an accurate report.  

During a walk last night, I did a test and used the option on my Charge 2 to track my walk, linking it with the bluetooth on the phone as prompted.  Using this method resulted in an accurate report in the app.  I'll need to test this again a few more times both ways to see if it happens consistently depending on if I initiate tracking on the App or the Charge 2. 

It's just a pain/extra step to have to pull out the phone and app to have the Charge 2 be happy while tracking. 

[Pjd1300]

@ELasater

Please post an update when/if you are able to replicate this.  

I Logged two walks today - one was spot on, but the other one was spot off!

Both were initiated from the app (like I always do).

[Brendar2016]

@DerrickS

Thanks for replying, appreciated.

The issues have been around as long of the device, the thread I linked to was opened in September last year. I accept that this is a known issue for Fitbit, but this is not recent, you have been aware of it and working on a fix for months now without success. All the while, the device is still marketed and sold as a fitness tracker.

To be clear, based on the very large amount of information available on these forums Fitbit have:

1. known about the issue since (at least) September 2016
2. Know the issues prevent it from doing the things that most people buy it for
3. Been unable to fix the problem
4. Continue to actively market and sell it (i.e. trade peoples cash for a product you know doesn't work)

I've tried all the fixes, they don't work (you know this). 

[Ddc9691]

The problem seems to happen when I stop the exercise tracking and the app compiles the data or syncs with my Charge HR.  I don't continuously sync the device with my iPhone 7.

[Mild_at_heart]

Me too - first ever -10K and it's showing under 7! 

[JNagano]

@Brendar2016 The strange thing in my situation is that my Fitbit Charge 2 worked fine from Christmas 2016 when I received it until February 22, 2017 or so. After that date, it started to perform like everyone has mentioned in prior posts, i.e., summary, split mile and average pace data are accurate right after the activity/run, but when a few minutes later when Fitbit synchs, the summary data is faulty, showing under-reporting of mileage and incorrect total time data. If Fitbit have known about this problem since September 2016 and i (along with a number of other users in this thread) only started having this problem in February 2017, then something is terribly wrong. 

[Kobalto]

There are two different problems:

1. Charge 2 incorrectly measures distance and pace when using the "Connected GPS" feature (starting the tracking from the Charge 2). The readings given while running and afterwards are incorrect. The strange thing is that the GPS track is recorded correctly, as you can see in the tcx file. Issue was detected in september last year. 

2.Fitbit incorrectly summarizes a run/walk (starting the tracking from the App). While running, the App shows correct readings, but afterwards the summary is wrong (although the splits are right). Issue was detected on february 22.

So they are different issues. The problem is that now you can't trust the Charge 2 or the App.

[tracey2]

Yep, it was a fluke. Today's 2.2 miles ≠ the 0.39 miles that showed up in my summary.

The summarized pace of 84'32" was good for a chuckle, but not good for accurate record keeping.

[Jueday]

Feb 22nd for me too

Moderator edit: personal info removed

[Ddc9691]

2/21 was the first time I see the problem.  Shows half the distance or less than the sum of the splits.

[ELasater]

I was able to replicate the problem.  Earlier this week, I tracked a walk initiating the tracking via the Charge 2, syncing it with my phone when prompted. The summary matched the mile splits. The iPhone was in my pocket with the app running in the background. 

Yesterday evening, I did the same walk, but initiated the tracking directly from the iOS app.  I grabbed a screenshot before ending the walk, and took a second one after finishing.  The summary is not accurate, but the initial tracking screen was and the mile splits are accurate as well. Again, the iPhone was in my pocket with the app running in the background. 

Edited to add: The inaccuracy started on February 22, 2017 for me.