[KNOWN ISSUE] Fitbit to Strava sync looses GPS track information

[ise]

Recently I face an issue that my Fitbit activities are not synced correctly. All the data are correct: distance, heartbeat and so on. But the GPS track stops in Strava after 2 km, no matter how long the track is in Fitbit. My last three activities face this issue and it worked before without any issue. 

I have already disconnect the accounts and connects them again, but without any luck.

Do any other Fitbit user face this issue or can give me a hint why this happens? It's annoying because it's start out of the sudden. I have attached screenshots of my last activity.

That's shown in Strava:

And this in Fitbit:

Thanks,

Daniel 

[Scout · Accepted solution]

👋 Hello everyone!

Thanks for your patience while we investigated this issue. Our team has found that the map being displayed on Strava is reflective of all the GPS data that was recorded in the file. This may mean that FitBit lost GPS connection and they are using cellular data to fill in the location for the remainder of the activity.

We would recommend that you make sure your device is up to date with the latest firmware and that your FitBit device and app are also updated. If, after recording a new activity, you are still noticing the same issue, please reach out to FitBit support for additional troubleshooting steps. You can contact FitBit support here.

[Liamxbc]

I deleted all the connections in Fitbit and Strava and then re-connected everything, seems to be working for now

[CycologistRal]

I had this same issue and can confirm the last 2 rides I tracked did sync the map correctly as of this past Saturday and Sunday. 

I noticed when the map was screwed up in Strava it was also initially missing in Fitbit. It seemed like because Fitbit was still rendering the map when the data was synced it didn't have all the info ready for Strava to render its map. 

I didn't change anything on my end, it just started working again so maybe Fitbit fixed what ever system that handles this process. 

[Liamxbc]

Yep I'm having exactly the same problem, used the same Fitbit for about 2 years and never had a problem until now. The above solution does not work!!!

[mdeviron]

Hi @Scout ,

I have the same issue as the other users wrote above, the map is correct on the Fitbit app but it is cut short in Strava (even though the distance is correct there as well). This has happened 3 times in the last week for me.

So it is not a GPS problem during the ride, but an import problem with the data. Like the others, if I delete this activity and import it again from Fitbit, it works correctly.

Kind regardsIn StravaIn Fitbit

[Ils1]

Hi @Scout, the issue is clearly not solved. Are you still analyzing this? 

[Scout]

Hey @Ils1, 
Yes, our team is still looking into this. As @Marc_ noted in a previous post, you can submit a help ticket and our support team can take a closer look at your activity. Please be sure to include the device & version you are using as well as the FitBit file. 

[Ils1]

I did!

[Ils1]

Hi! Are you still investigating this issue, because the issue is still there

[Dudebro58]

Scout, 

while the problem *may* end up being on the Fitbit side, some of these “explanations” are just dumb. I’ve told you before (as have many others) Fitbit is collecting the data, including GPS, correctly, accurately and completely. The file you are importing is truncating the GPS data from THE EXACT SAME POINT in the corrupted uploads. In addition, the problem is intermittent. 
I suspect the code or the environment on one of your servers (or Fitbits) that handles the integration has a bug or limitation that is dropping all GPS data after a certain point. 
Asking US, the paying customers, to troubleshoot this issue with your integration and to run interference with Google, one of the wealthiest corporations on the planet, is lazy and shameful!!  Any IT person worth a crap can easily setup a Fitbit test account and within a couple iterations, duplicate the issue. Whoever is feeding you this “cellular AGPS” nonsense does not give a crap about fixing the problem. Find someone that does.  

[klstrava]

This is super annoying, Scout! Is it only an issue with FitBit or other trackers? Thanks!