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.

[ClaudineAlta]

Same problem here...I just walked 4.7 miles (tracked on 2 different online maps and the iPhone Health app thing) in 83 minutes, which is a 3.4 mph speed--completely accurate for me. 

My Alta got the minutes correct, but gave me 2.5 miles, which is a speed of 1.8 mph...absolutely wrong. 

I'd love to hear someone's take on why this is happening. 

[Lindag199]

Thank you @mnkyd41 but we are telling it to track the run/walk. It is not deciding if we are exercising. I deleted my Nike Running app when I started using the Fitbit app to track and map my course.

[Lindag199]

I'm curious at to why we haven't had any help from the moderators to this thread or this one: https://community.fitbit.com/t5/iOS-App/Exercise-tracking-error/m-p/1843157#M56009

[Julia_G]

Hi, @Lindag199, there have been a number of posts about this discrepancy, and I will move this thread to the one where a moderator is looking into the issue.

[Julia_G]

Hi, all, this looks like an issue that is affecting a number of people, so I am moving this topic to the one that a moderator is currently collecting information.

[Julia_G]

I think this might be related to an issue some others have experienced, so I have moved this post to the other thread where hopefully you can get updates.

[Julia_G]

I think this is related to an issue others have reported, so I have moved this post to a thread that a moderator is currently monitoring and to keep all instances together.

[Julia_G]

This seems to be an issue others have experienced, so I have moved this post to a thread where others have reported something similar.  That way everyone can have updates.

[Lindag199]

Thank you @Julia_G!

[Kobalto]

Whatever is causing this, I believe this has something to do with fitbit's severs and not the app or the tracker. At least I've checked the tcx files (that can be downloaded from the web page) and the distance is the right one, not matching what is displayed. Also while doing an exercise, I've checked the app and it was showing the right distance. Its only after the run is finished, and the app syncs with the server, that the distance goes wrong. Also, it's weird that the pace you see in the web page is different than the one you see in the app (in my case the web shows the correct one), although the distance is wrong in both.

[Jess_K]

 I ran about 2.2 miles today and used the gps exercise tracker on my Fitbit Flex 2. I ran on two roads, and on each road, I turned around along the same path. The gps tracked that I ran on the roads twice, but the total mileage says only .17 miles. Is there anyway to change the overall mileage? Or a way to have the app recalculate?

Thanks!

-Jess

[Pjd1300]

Interesting...  Fitbit's servers...  Is anyone else thinking this could be "Cloudbleed"  related?

[Lindag199]

Interestingly, my stats were correct today. I walked under adverse conditions, 40 degrees and 15 mph wind, so I was slower than usual. I was shocked to see my distance was correct? The inconsistency is driving me crazy!

[Rufury]

Same issue today:

1. 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)? 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? Apps GPS

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

[Duckpizza]

I am appalling with tech related things, but the fact that everybody seems to be saying it started happening around Feb 22nd would suggest it has something to do with Fitbit servers and the final sync. I have voice cues telling me how many miles I have walked and since Feb 22 nd it counts correctly right up until the point I finish, but once it syncs and registers a tracked walk is complete on the app, it gives me a completely incorrect distance, although all the splits are correct. Pace is completely off too.

Sent from my iPhone

[AlvaroFitbit]

@Brendar2016 Thanks for stopping by! Sorry to hear about your issues with the Connected GPS feature. I suggest you update your tracker's firmware and retry using the app, allow enough time for the phone to properly connect with the tracker to record your activity and GPS information. If you continue having issues then please contact our Support Team for assistance.

Let me know how it goes!

[Soph95]

Hello

First sorry but I am French ...

The problem happens when I "follow" physical exercise

When I run there is no problem (time, distance, rythm ...) But as soon as I save the exercise, the datas are changed and get wrong.

Oops ! 200 m for 41:44 min, I must be something like a snail ?

[majbugman]

NO, NO, NO, NO!  Please do not blow this off FitBit.  There have been 240 more posts in the other thread since this was marked as "solved"  It is not solved.  I know i have the latest firmware and have restarted my watch and my phone. Waited for the watch to link to the phone before I started etc.  If we need to do backflips to make the connected GPS work then that is bad engineering.  Fix it please. 

[Julia_G]

Hi, @Soph95, I think this may be related to a similar issue some other users of the iOS app are experiencing, so I am moving your post to that thread so you can get any updates posted.

[Julia_G]

Hi, @Jess_K, I think this may be related to a similar issue that some other users of the iOS app are experiencing, so I have moved your post so that you can get any updated info on this issue.