Closed lexicalninja closed 4 years ago
@Lucylea Has this issue occurred more than once, or just the one time?
I have only tried once, and it crashed, maybe I will try it tonight
The bug also exists in 2.5.1 version I tried the same workout tonight, and it seems to crash at the same position, that is in 14 minutes, where the second cool down end and the second interval begins. BG HG Tempo 3*15
---Original--- From: "lexicalninja"<notifications@github.com> Date: 2020/3/31 22:05:55 To: "kinetic-fit/fit-android-issues"<fit-android-issues@noreply.github.com>; Cc: "Lucylea"<497717576@qq.com>;"Mention"<mention@noreply.github.com>; Subject: Re: [kinetic-fit/fit-android-issues] Workout crashed mid workout. (#23)
@Lucylea Has this issue occurred more than once, or just the one time?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.
Smartphone (please complete the following information):
Oneplus 7 Android 10 Kinetic Fit Version 2.5.2 Trainer (please complete the following information):
Trainer: Road machine 2 Sensor inRider, old black one firmware: version 2.0 Additional context no
@Lucylea I think I may have found something that was causing this, but am not sure. Please update to 2.5.4 (235) when it becomes available and let me know. Thanks.
Yes, you made it! It would crack mid training until I updated to 2.5.4
Excellent!! Thank you for your help fixing this.
Describe the bug Today I select the workout BG HG Tempo 3*15 as training, and it suddently broken down when the training is in progress.
To Reproduce Steps to reproduce the behavior:
Expected behavior I can finish the BG HG Tempo 3*15 with result displayed, so I can export the data to training peak
screenshot Smartphone (please complete the following information):
Oneplus 7 Oxygen OS 10.3.1 Kinetic Fit Version [e.g. 2.4.1] Trainer (please complete the following information):
Trainer: Road machine 2 Sensor black one Additional context no
Originally posted by @Lucylea in https://github.com/kinetic-fit/fit-android-issues/issues/20#issuecomment-605589734