I am using an ipad with a kickr v5
same equipment as ever never had the issue until the past couple months
We made a change to a faster react native javascript engine a few months ago, but now we are reading that in some cases it might be slower. For any programmers we went from VSC to Hermes. 
We are going to see if we can switch back to VSC and compare performance with some benchmarking software. We also switched from CPU based charts to GPU based but for sure that seemed to improve performance in profiling and allow longer workouts.
@cyber-nico @Francois2023 Would you guys be willing to test for a week with a JSC version of our beta app? I would need to invite you to Apple Test Flight version. Let me know and you guys can send me email or personal message here with your apple email address and I will invite you. Really since we canât duplicate this, itâs impossible to know how to fix it. We can do this hack but it would be ideal to first solve it the âright wayâ and then add the hack for emergency situations. I am suggesting you guys because you guys are both seeing it on shorter workouts. And right now I donât know anyone else having this problem. No one above has confirmed still having an issue.
Hi Alex, of course, no problem, I would like to help. If I send you a message via the âMessageâ function in this forum is this private? I would like to avoid making the mail address publicâŚ
I think I also ran into this today - started a ride at 7:15am, got off the ride at 9:15am but TD only recorded 1.5 hours. I noticed the seconds seemed to be ticking by slowly. No other apps running on Android, battery at 81%, and it was a steady state ride with no power spikes. Link to ride
Sorry to hear that.
We have new version that one of the guys above confirmed in beta works for him so hopefully we have this solved. We will launch it tomorrow or Monday to everyone and see.
So thanks to both @cyber-nico and @Francois2023 it seems changing javascript engines has solved the slow downs. We will launch this to everyone in the next day or so and fingers crossed this is it!!!
This morning 6h of workout and 0 slowing timer !! 
Sounds great. You are an animal, 6 hours indoorsâŚ
Ahah Itâs easier indoors in the warm than outside in winter.
2 Likes
Ok new version of our app is out. As I said fingers crossed. So far it seems to work good to our two that recently had a problem.
It happened again: during a long (90 mins) session, after the 75th minute (more or less), the timer started to slow down, stop, restartâŚ
hitting the right arrow (to skip what become an endless segment) the timer started to speed up trying (i guess) to recover the gap.
how far are we from solving this bug? thanks
I am not sure if you have latest version from yesterday (4.2.2). But so far you are the first person to report this issue with this latest version (and 3 other people have stated that it seems to be resolved for them). What phone/device do you have? How was battery charged? Doing anything else with the activity? Can you send a link to the completed activity from our website?
I moved this to the other thread discussing this.
Not sure if this link works https://app.trainerday.com/activities/6552750e5c84aefd0780f1c2
I had the 4.2.2 running on a Ipad pro. battery was almost 100% at the beginning of workout and the workout was evertything I was doing with the device. thanks
Thatâs depressing. Fast device and it slows down. We are sure this is something related to iOS that it starts running some heavy processes that take away power from our app because we have run 100 tests even on slow devices and it works perfectly. I have iPad mini V1 and it 90 minutes is no problem, absolutely accurate to the second. So we will wait a little longer but I have a âhackâ idea that should solve it once and for all, meaning it will at least be accurate duration to within a few seconds of the whole workout.
Another 2h workout this morning, cast on PC actived and 0 problem ! 
1 Like
During yesterdayâs training, I noticed that in 30-second intervals, the displayed timer would stop for a second or two and then make up for lost time. It was during the countdown and, for example, when displaying 10:31, it stopped and then quickly jumped to 10:28 or 10:27. The same thing happened at 10:01 a.m., 9:31 a.m., 9:01 a.m., etc.
The whole thing ended at the correct time. 
Yes that is the ânormalâ behavior and the nature of how our technology works with there are inconsistent timing slow downs. Peoples devices should only temporarily not be able to handle the load. Why these devices run long slow processes that slow it down, I just donât understand.
Not sure if itâs the same issue, as he stated that timer speeded up later again, and (tried to) close the timing gap.
Because I had a similar problem, but no inaccurate timer at all, instead the app was getting really unresponsive and therefore the timer was getting slow. It then speeded up again, and in sum the time was correct.
But during the unresponsive behaviour the app completely slowed down, drawing the graph lasted forever. Timer didnât update or not in seconds, but speeded up later again.
So maybe drawing the graph for the whole workout needs a lot of memory?!?
It was a 90m+ workout and running 75m in background. Getting to foreground leads to getting unresponsive.