Marc, this is NOT an AGPS problem. 
Are you in IT? Do you think it’s a coincidence that whenever the GPS data drops out if the integration it’s in the exact same point in the file? 
set up a test environment with a Fitbit and actually look at what is happening instead of speculating or asking us to do your job for you. 

Hi! I have exactly the same problem since a few weeks. All information is in the fitbit app, but strava syncs everything except for the gps info.

I have a fitbit charge 5. Are there any updates on this already?

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

Hi Marc, the issue is clearly not solved. Can you please dig further into this?

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

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. 

I did!

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 regards

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. 

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

I also have been having the same issue but it doesn't happen every time - only sometimes whilst walking. The first day I noticed it happening was 19th July.

I end up deleting the activity on Strava and re-sync it using https://www.fittostrava.com/

It comes up perfectly after this. 

Hello,

App is up to date and still facing the same issue. Can you please provide a solution. It seems many people are facing the same issue. GPS data are correct in Fitbit but there is clearly a problem when uploading them to Strava.

without a solution, the Fitbit is useless so I count on a proper solution.

Thanks,

Veerle

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

I compared 1 successful run and 1 not successful run by exporting the tcx file from the Fitbit app and there is no difference in the file format or data type. The issue is clearly the synchronisation!

Temporary fix I found is to export the tcx file from the Fitbit activity, uploading it to Strava entering a manual activity after deleting the original one and voilà.

So far I'm having the same issue happen on and off. I had a few successful uploads yesterday but today it didn't have the map. When I looked at the activity on Fitbit the map wasn't there at first. It took several seconds for it to load. I suspect the map data isn't being processed when the activity is saved on Fitbit until the user looks at it. Here's a screenshot of what I was seeing. 

That's interesting. Maybe it is trying to push the activity to Strava before it has finished processing it? 

Yes, I guess so too. I had same experiences.
Just after stopping logging,Fitbit app sometimes shows inperfect training history. 
That gets perfect in a few minutes.

Same issue here from pixel watch. Can re upload to get full map but it doesn't show when syncing from Fitbit app. Dont make the same mistake as me, if you ask Strava to fix the distance it doesn't fix the map and shortens the distance. Predictable, but thought I should check! It may be a coincidence but seems to have started about the time I subscribed to Strava. 

I'm getting the same problem. Started this summer. 

I am getting the same problem. The metrics shown in Strava for the walk are correct, but the route shown on the map is incomplete. I exported the .tcx file for the walk from the Fitbit app and imported it into plotaroute.com and the route shown there is complete. So it is not a problem with data exported from Fitbit.

It happened to me again this week but this time I actually looked at the incorrect map a bit more closely. The erroneous map was from a run I did with a running club. They have mixed ability and tend to stop and take occasional breaks. My watch is set to auto pause. The place that the map stops is one of these break points. The watch asked if I had wanted to end the run there, I said no and it kept recording but I wonder if this is part of the problem. The map is wrong in Strava but again the tcx contains correct data. For some reason Strava seems to end the GPS tracking there. I am guessing it stops looking at the GPS after a period of inactivity. Does this correlate with anyone else's experience too?

Hello All! 

Marc here with another update. Fitbit's team has confirmed with us that they are still working on this issue regarding data/map discrepancies in the activities that they are syncing over to 3rd party connections, like Strava. 
We still do not have an ETA from them about a fix but they have added the issue to their status dashboard last week: https://status.fitbit.com/incidents/D6j3uhKPGKKsJjNoxsp7
You can check there to see if the issue is still ongoing otherwise I will also post a follow-up here in this thread once we get word that the issue has been resolved by Fitbit. 

Thanks for the patience and understanding all! 

Hello all - apologies for the delay in communication here, but this issue is fully resolved. Please let us know if you have any more questions! 

I think it has not been resolved yet.  I went for a run on 16th June 15km. However, Strava picked up 14.89.  In Fitbit watch it is 15.08. 

I noticed that GPS data sent by Fitbit is wrong. 

Thanks.