Skip to main content

Hi Strava Team,

Our application encodes .FIT files from pool swim activities and sends them to Strava via the API

We recently found some swims that have an incorrect Pace and Moving Time, after some investigation I noticed that in the ‘Laps’ list for the Strava activity it only lists 36 out of 63 Laps defined in the .FIT file, the ‘moving time’ is calculated from these Lap messages so its short.

There are no other errors shown on import

I have spent a lot of time looking at the FIT fields and they look correct, please could someone take a look at the attached .FIT file to see why Strava only seems to read the first 36 Lap messages when there are 63 in total?

When I import the same .FIT into TrainingPeaks it reads the whole file and gives the correct swim pace 

TIA

 


FYI ​@Lola ​@Marya ​@Bryant ​@Kimberly22, this sounds like a possible bug, could we please have someone from the product team have a look? Thank you!


Reply