In Strava WEB there is a lap of 20min 40 seconds, and if you look at the same activity in Android app, the lap is shown as 20min 00 seconds. There are 40 seconds of diference. I would like to show you the screenshots but you can check it by yourselves following the link.
¿Why this big diference?
I asked this because we had an api integration with Strava and we have the 20.40 data, and de client wants the 20.00. Its an FTP test, and there is a big difference.
Thx in advance
Page 1 / 1
That sounds like an interesting bug.
When looking at the activity, it looks like all laps except one are different. Comparing web to the app:
43:33 (43:00 in the app)
5:00 (5:00)
20:08 (20:00)
20:40 (20:00)
10:13 (10:00)
3:29 (2:37)
The app seems to be rounding down the lap times for some reason, AND the total time doesn't match either (web: 1:43:03, app: 1:40:37, if I’m counting it right). My initial thought was that one works with elapsed time and another with moving time, but that none of the totals actually correspond with either (moving 1:41:02, elapsed 1:43:04).
Strava might need to have their developers look into it...
@Calamyty It’s a moving/elapsed time problem, you can see in the web app in the analysis of lap 4 that there was a 40 second pause:
@Jan_Mantau initially I thought it might be it but then tried to add up all laps times - the web total seems to almost correspond to the elapsed time (just one second off), but the app total is shorter than the moving time. So if it's a factor (but that would be a design flaw - both app & web should use the same, not moving in one and elapsed in another), still the app laps are off.
@Jana_S Strava calculates moving time differently in laps and segments on one side and the activity as a whole on the other side. The wrongly calculated moving time of activities is in my estimation the most reported error in the hub and Strava either ignores it or make excuses.
