Another one to report this issue unfortunately. All the GPS data is present in the fitbit tcx file; as Dudebro58 says manually exporting this to strava will show the full route. Seems like an issue with the syncing to me.
Thanks
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
Same issue here! Since a few days it often shows incomplete GPS in strava, although the map is complete in Fitbit.
Yes, I've also seen this.
Downloading TCX file from Fitbit and uploading it seems to produce the correct path though.
I have exactly the same issue which only started recently.
I'm having to do exactly the same. Couldn't agree more with what you've said 👍
This works. Thank you. Old submission must be deleted first
I have same issue. Fitbit data is perfect, but GPS data automatically uploaded to Strava is incorrect.
Interesting thing is that automatic sync went well yesterday but it went wron today.
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.
Just posting here as another person that is encountering the same issue. My cycling works sometimes but mostly cuts off after a few kilometers.
I ride most days and it seems that it started on July 19th
Thank you all for your posts and sorry for the trouble.
As a reminder, if you would like our team to take a closer look at your activity, please submit a help ticket and send over the FitBit file to our support team. Please be sure to include the device & version you are using as well and our team will further investigate.
I have exactly the same issue and this is frustrating that it is marked as Solved and just mention go contact another support...
I believe like many other folks here, our Fitbit devices are up to date with the latest firmware and software.
The issue is clearly either on Strava side or something changed from Fitbit and the integration needs to be reviewed. Please take a look at his and keep us informed of the progress of the resolution. Thanks
I'm having the same issue the last few weeks. It just happened to me again this morning so the issue is not resolved (I've checked for app updates, restarted my phone and watch etc).
Seems to be a problem with the sync between Fitbit and Strava. Specifically syncing the <LatitudeDegrees> <LongitudeDegrees>
As others have mentioned I am able to manually upload the .tcx file and it works. This means that Fitbit is correctly recording the GPS coordinates. It also explains how the map is correct in Fitbit.
Downloading a failed sync .tcx from Strava shows the GPS coordinates are all the same after a certain point in the ride. Interestingly all other data like <Time> <DistanceMeters> <HeartRateBpm> seems accurate.
Obviously nonsense. As other posters said, if you delete the auto-synced activity and re-upload manually, the issue is fixed.
I submitted a ticket to Strava Support as I thought this community is independent from Strava.
It's not dificult just access to the page from below link.
After chatting with chatbot, we can ask questions via email.
When Strava gets same questions or requests from many users, they prioratize it.
That might solve the issue immediately.
Hoping Fitbit users here request a lot.
https://support.strava.com/hc/en-us/requests/new
Hello All,
Marc following up again. Thanks to all of you who have reached out to our support team. After additional investigation and testing, we have confirmed that the files that Fitbit is syncing to Strava and other 3rd party apps are missing GPS data in those TCX files when compared to the GPS data in the files that athletes manually exported from Fitbit. We have done some extensive testing this last week and have been able to replicate this issue, and we have reached out to our contacts at Fitbit and they are investigating this further on their end.If you are currently experiencing this issue please reach out to our support team and include the following:
- a link to your activity
- a copy of the exported TCX file from Fitbit for that activity
- your Fitbit User ID
You can find your User ID in the Fitbit app by going to the 'You' tab and tapping your name, and that will take you to the 'About You' page where you can find your user ID at the bottom of that page, you will want to copy or take a screenshot of that ID and provide it when you
submit a Strava support ticket.
Thank you all for your patience, when we have an update from Fitbit we will post it in this thread!
I found exporting the file from Fitbit, deleting the activity on Strava and then uploading that activity file successfully restored the full map and all the data.
I've just had the exact same issue today. My run 3 days ago was fine and as were all previous. I've followed this same route multiple times with no issue so I don't think the GPS is the problem. Hopefully sorted soon 🤞
I'm a bit late to this thread but I want to say I am having issues with my Fitbit versa 4 data pulling through incorrectly.
For the past 7 activities it's undercut my milage but roughly a mile. GPS single not lost at all, map has pulled through but milage, pace, heart rate all wrong. I have reached out to support however they are saying it's a loss of GPS and to do upload the TCX file. Tried this, shows that GPS wasn't lost, yet still being undercut. Not really sure what to do as this happened to me before, I found not hiding my start and end points helped, but it's gone back to incorrectly pulling through. Still awaiting an answer from support. Has any one had this issue resolved?
This is super annoying, Scout! Is it only an issue with FitBit or other trackers? Thanks!
can you give some directions for how to do this? thanks very much!
If you mean how to manually fix:
1) delete bad activity from Strava. You can’t load the good one until the bad one is gone.
2) go to Fitbit app. Locate your activity (bike) open up. There is a menu in the upper right I think (…) that has the option to export as TCX. Pick that. Save to Files (or a place you can remember how to get to iCloud, Dropbox, OneDrive, etc.])
3) Strava won’t let you load a tcx from the app (LAME!) but it will let you load from the browser website. So open chrome or safari or whatever and go to www.strava.com. Login and then from the “hamburger” (three horizontal lines) scroll down til you see Upload activity.
4. the font is teeny but you want to pick file, then pick the file you exported from Fitbit (should be in files if on iOS). Then scroll down and find the save and view menu.
Should appear in the app now and you can edit the name etc.
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.
