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!

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 🙂

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!

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

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.

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

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.

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

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.

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

Thanks

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

Thanks for the reply. It seems strange that multiple users have started reporting this issue, and there seems to be some consistency in distance recorded before the route is truncated - If it were a GPS drop then surely it would be random.

Has there been a change Strava side to only accept GPS data and not locations taken from cellular location? 

Sorry, but that's not true. If I export the tcx file from Fitbit manually everything is alright and all GPS points are correct. I can display it in any other track viewer.

If I download the tcx file from Strava, about after 1.6km all GPS points have the same coordinates, but different heartbeat values and distance. So, it's not a problem on the Fitbit side. At least not on the source tcx file. I don't know what happen during Fitbit Strava sync with the file. 

If I import the file manually into Strava everything is fine and the track is displayed correctly.

So it's definitely not a solution what you have posted. 

I think that assessment is incorrect. The posts here show the fitness tracker is recording the information correctly but it is not being transferred to Strava in full. I can send data from two bike rides to back this up. It's clearly not loss of GPS that's causing the issue. Sorry.

I agree with other users. My Fitbit app shows my entire route/GPS data whilst Strava does not ergo my tracker is recording GPS data and transferring it correctly to the Fitbit app but not Strava. It's therefore more likely an issue with Strava importing the GPS data.

Hello All, 

I am Marc, and while I am not a moderator I am part of the Strava team and want to provide some additional insight into what might be happening in these affected FitBit activities. 

At no point has Strava been able to use AGPS (assisted GPS) data that uses cellular connections to help pinpoint location. We require the actual recorded latitude and longitude points to generate the map that you see on Strava, while some devices can generate maps and data using only the cellular location that data is not written into the activity files that those platforms (in this case Fitbit) sync to Strava. Unfortunately, if the GPS data is not written into the file we do not have a way to display that missing portion of the map for your activities, and do not have a way to fill in GPS data after a file is uploaded to Strava from these partner applications. 

To further clarify the other question about if Strava is changing the files, Fitbit manages both the recording of the files on their devices/app and the files they are syncing to Strava. Strava does not edit or change the original TCX files that Fitbit syncs to us in any way upon upload to your Strava account, we only display the data that is in those files. 

If you would like for our team to take a closer look at your activity, please submit a support ticket and our support team will be able to assist you.

Hi @Marc_ - Thanks for the additional reply, please can you advise why these GPS drop outs all seem to occur at almost the same distance in to the activity (roughly one mile from what I have seen); and why this issue has only started occurring in the last few weeks?  

Something has clearly changed 

Thanks for your reply.

Sorry to say, but something has clearly changed otherwise not all users from this thread see the same results and at the same time frame.

And I say it again. If I have a look into the source tcx from Fitbit all data points are correct and they were not recorded with AGPS. The GPS connection was on all the time and in the TCX file from Fitbit everything is correct and the data points are not marked as AGPS recorded data points in any way, so the structure look exactly the same throughout the whole track. And each position differs from each other. 

If I download the TCX file from Strava, the TCX data points are correct until about 1.6km and then they start to be the same location all over again until the track ends, that's the reason why the track stops after 1.6km. The data points and the location are there but all at the same latitude and longitude after 1.6km. 

If needed I can provide the source TCX file from Fitbit. 

But please stop marking this thread as resolved with answers that are not really satisfying by saying this has something to do with the tracker. They work without errors for two years now!

At the Fitbit community a thread was started about this issue, too. Here is the link for reference.

Hi All,

So after experiencing this issue the past few days I resorted to the old IT help desk default response; I shut down my Fitbit, I shut down my phone, then turned on my phone again followed by the Fitbit. This appears to have corrected the issue as full GPS data for my evening ride has successfully turned up in Strava. 

• Same problem. If I delete and manually upload it’s fine. 

This is an incorrect analysis. All the GPS data IS in the Fitbit file. It has happened to me six or seven times in the last week. Each time, deleting the synced Strava activity, exporting the Fitbit tcx and manually loading it via the Strava website, solved the issue.  So… look at your sync again. Something is corrupting or truncating the file during the sync process.  

Hi Marc

i am experiencing the same issue, although not every run. My runs on Saturday, Tuesday and today (Wednesday) show the map for around the first kilometre only but distance, duration, speed stats for the whole run. The runs were completely recorded on Fitbit including the full maps. My runs on Sunday and Monday were transferred ok to strava. I have a Fitbit charge 5, both Fitbit and Strava apps are up to date, as is the Fitbit firmware. I’ve also restarted the Fitbit device. So I think it points to some issue at the strava end

@Dudebro58, @ise, @wcarlton, & others...
As @Marc_ noted, 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. 

The Hub is great for general questions and information while our Support team will handle questions that require account access and analyzing personal activities or account data.

I too am experiencing this issue. Pixel watch. Fitbit is fine. Strava map is cut short but everything else seems fine. Even had one activity where no map copied over. Please reach out if I can provide more details!

Thanks for looking into this.