During development of my Datarun plus datafield I come across the fact that info.elapsedDistance starts counting in the simulator after a FIT-data simulation is started. It should start counting after the start button is pressed, but it starts earlier if the simulation starts earlier then the button-press for start.
Are you using simulated data or playing back a .fit? Which SDK?
When playing back a .fit, if it was recorded with "smart recording", you might not get data for a few seconds, and then only get updates every few seconds.
Also, there used to be a bug when playing back a .fit, the distance was in feet and not meters. This bug was from a while back, and to be honest, I'd not checked if it's been fixed, so that may be involved.
It is with simulated data and SDK 2.3.5. It's not an issue with metrrs versus feet. I see with println after 1 second after the start of an activity directly that info.elapsedDistance has more meters than is possible with the current pace for that second. The longer I wait after starting the FIT-data simulation, the more meters are there after one second of activity. After that first second it behaves normal, so that every second the distance grows according to the current pace
It sounds like you might have a bug here. Could you follow the Bug Reports Forum Rules format including a reproducible test case? With the growing number of developers and features we have this really helps us to better address issues found by our developers. You can send any info needed to [email][email protected][/email]
