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.

[Mtnbuckaru]

I bought a Garmin Forerunner 235 today. I'm beyond annoyed with this problem as it severely interfered with my training schedule. At least there is a service to sync this with the Fitbit app. The Fitbit GPS feature is useless right now!

[rdebell324]

I am having the same exact issue. Total mileage does not add up accurately, pace is off and active minutes is off - but I will spare the details since we all know the problem. I just wanted to add that the problem just started for me on Sunday (3/6/17). My walks on 3/4 and 3/2 seem accurate.  All 3 walks were the same approximate route. 

[kl_w]

The issue started happening for me on 26th February. Similar to some others, my runs involve running to a specific point then turning round and returning. The splits and voice feedback are accurate, the total distance is much less than the actual.

The first time this happened, the app popped up with a 'Poor GPS Signal' message just as I was starting my run. As the weather had been very bad I just put it down that. However, the same issue has happened on a further run, this time the app did not display a popup. 

iPhone 6

iOS 10.2.1

Upgraded to app version 2.33 and the issue still occurs. 

[BBrick]

I have been having problems with distance run and what is recorded after you finish the workout. The display will show the correct distance when you press finish but after it syncs, the distance shown is much shorter which in turn makes pace slower too. The details in the workout by mile are correct so it doesn't make sense howcthe total can be wrong. Please research and fix this problem!!

[ChelFB]

I added a topic earlier today for this exact same problem. Would love an answer soon.

[Duckpizza]

I often got the "poor GPS signal" when setting out for a walk, and it never used to be an issue with the accurate logging of distance and pace. My tracker stopped working on Feb 22nd and has not worked correctly since and it must be some issue with Fitbit in view of the sheer numbers of us having the same issue, all starting at about the same time.

Any news on a fix, please, Fitbit? 

[Trudy1967]

I have the same issue on my Iphone 7 (iOS 10.2.1) with Charge HR. For example:

- last monday: total distance 3,09 km and kilometer splits 10,49 km. 

- last sunday: no differences

- last friday: total distance 0 km and kilometer splits 6,48 km

- last wednesday: no differences

- all days before: lots of differences

[AnSmith-1974]

I have had this issue for about 2 weeks now like everyone else and I updated the app today went for a run and it's still wrong! So no nothing's resolved Fitbit 

[Kobalto]

It's not so bad. I've also updated, and I was very happy to find out that now I can easily share trainings that are completely inaccurate. Today I ran 10k in exactly 4.37k.

[JamesW123]

For the developers,

I noticed today when this failed again (I ran 5K and it only recorded 0.28K) that for a brief moment when opening the run after completing it in the app the distance registered matched what I had done then suddenly updated to be 0.28KM.

It only showed the initial correct distance for probably less than a second. Is it possible that something is over writing the distance straight away after uploading it?

[Hades74]

French user, also involved by this issue /

Iphone 5S

Last app

iOS 10.2.1

W10

[Mild_at_heart]

I rang Fitbit yesterday and they agreed to organise a full refund from my retailer because of this. I'm taking it back today and thinking of buying a garmin . . .

[Mtnbuckaru]

I just bought a Garmin Forerunner 230 for when I actually run because of this issue. For daily activity I'm sticking with my Fitbit and I just manually log my runs from my Garmin. Fitbit, you better get your act together before you start losing business big time.

[AnSmith-1974]

iPhone SE

charge hr

[AnSmith-1974]

iPhone se 

10.2.1

charge hr 

no resetting the tracker or force quitting the app helps at all 

[VictoriaO]

I just got a Fitbit Blaze and it is way off in tracking my steps. It says I have walked 1230 steps today and I have only actually walked less than 300 steps. What can I do to have a more accurate reading?  

[VictoriaO]

I just got a Fitbit Blaze and it is way off in tracking my steps. It says I have walked 1230 steps today and I have only walked less than 300 steps. What can I do to get an accurate reading?  

[SunsetRunner]

This is still ongoing. The distance logged doesn't match what is being shown in the app.

What type of iOS device are you using? iPhone 7

2. What iOS version is your device running (ie iOS 10.2, iOS 8 ,etc)? 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? Charge 2 using Apps GPS

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

[SunsetRunner]

This is still ongoing. The distance logged doesn't match what is being shown in the app.

What type of iOS device are you using? iPhone 7

2. What iOS version is your device running (ie iOS 10.2, iOS 8 ,etc)? 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? Charge 2 using Apps GPS

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

tracking walk just before stopwhat the app saw

As you can see the tracker saw 1.59 miles, but when finished it showed 1.08 miles even though it did record the 1.59 miles in the split. Its confusing and has only really been happening sinc the recent upgrades came out. Until then it recorded andd reported what was on the screen.

Awaiting an update with a fix please !

[Bajora]

I find this completely ridiculous! How could Fitbit make such an error with a FW update and ruin one of the fundamental functions of their product?! I have been using my Charge HR for over two years and when mine started underreporting the mileage a few weeks ago, i figured it was just my well worn Charge HR dying. I was ready to order a new and improved Charge HR2 but thought I would sniff around online a little first to make sure it was my watch. Then I found this thread. 

I own a Blaze also ... but I am completely agog at Fitbits failure here! And two weeks later they still have not solved it?! How about offering a simple roll back to the previous FW that worked?