[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.

[ise]

It's good to see that I'm not the only one with that problem. It's nearly at the same time as you described where my Fitbit tracks are cut off after 2km, too. 

I have a Charge 5 which worked fine before. So, there must be an issue during import, maybe Strava cuts off something or Fitbit does something different since then. 

Would be good to hear something from Strava if there is an issue with automatically import from Fitbit or if there is a general issue with the import!

[ise]

Maybe anyone of the moderators have some more insights to this. Sorry @Bryant, but you were the first moderator I have found 😉

[Nico1090]

Hi all,

Same problem here, it starts to be annoying. Would be great to have it solved, I am pretty sure (hope) support team is working on it?

Cheers,

Nicolas