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

[Jayebur]

I am getting the exact same issue starting over the weekend. It's really disappointing and hoping we can find a fix soon.

[Jayebur]

I am using a fitbit charge 5 connecting to Strava through an Android Nokia, maps are stored fine in my fitbit app but move over to strava incorrectly. the length and distance is correct.

[Slarah]

This is happening to me too. It won't upload new activities either. I've reinstalled both Strava and Fitbit apps, which hasn't solved the problem. I cannot reconnect my Fitbit charge 6 with Strava now either.

[Scout]

👋 Hello everyone!
Thanks for your posts. I'm going to check with our team about this. I'll report back once I get an update. 

[marrinr]

Hi,

I have exactly the same problem. Approxiately 1 mile of fitbit data shows on the strava map.  Strava holds an accurate record for distance, heartrate etc. but does not show an accurate map.  I have found that I am able to export the fitbit file and import the tcs data and all is OK - the map shows correctly, but this is going to be really annoying if I have to do it for every new activity.  Please could you update if there is a fix or anything that we can do.  Many thanks.

[Disco181]

Hey Scout, do you have an update on this issue. I'm experiencing the same issue.

Thanks

[Indrehus]

Hi!

I have experienced the following three times now. It seems the data automatically imported to Strava from my Fitbit Sense 2 is incomplete. Below are screenshots of the same activity from the Fitbit app and the Strava app. As can be seen, the GPS data seem to be cut-off after a short while in Strava. Last time I experienced this I could fix it by manually exporting the GPS data from Fitbit and manually importing it into Strava. It seems the three times this has happened was when I started a new activity shortly after ending another one. Not sure if this is related. Has anyone experienced something similar? Is there a way to fix it? It is quite impractical to have to manually verify and fix such cases. Thanks!

[jason2600]

Same here. Thanks for posting it.

I just updated Fitbit and Strava to the latest versions before my last ride, but that didn't help.

My last ride that worked right was July 15. July 17 and every ride after didn't map or track segments correctly. I'm using a Fitbit Versa 3 syncing through a pixel 7 pro. I see iPhone mentioned in the thread, so the bug seems platform independent.

[scoopi]

Hello.  I have exactly this same issue, I completed a 15.58km hike this morning however only the first 1607 metres are shown on the Strava Map.  The Fitbit map shows the whole route.

A few days ago the same happened, a 10.41km run, but the Strava map truncated at 1609 metres.  The activity before that, a Walk, truncated on the Strava Map at 1603 metres. 

It’s only the map itself that seems to be impacted, all the stats, including distances, in Strava are correct. 

My Fitbit is an Inspire 3, Fitbit App is v4.21, Strava v368.0.1 and using an iPhone 13 running iOS 17.5.1.

I first saw the issue on July 12th 2024.

Would be interested in a fix for this too 🙂

 

 

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