Problem with results of a workout
Submitted by Zw426p on Sun, 2014-01-05 15:39
| Assigned to: | Ransom |
| Created: | Zw426p at Sun, 2014-01-05 15:39 |
| Status: | Closed (Bug / Priority Normal) |
| Case ID: | IMobileIntervals iphone application: 503-10336 |
| Last modified: | Mon, 2014-01-06 11:17 |
Hi,
I've just started using iMobileintervals on iPhone. I really like it. I have setup some workouts and also completed a couple.
The workout called - 'Week 1 S2 tempo' seems to have a problem. The workout went OK, but the results file seems to be corrupted. The workout lasted 1hr 15mins but when loaded into Garmin it says 14:59.
Also, when I try and open the results on IMobileintervals it seems to lock-up the website.
I have exported as FIT and GPX and tried in other apps with the same results - GPX fails.
Any thoughts?
Many thanks
Mil
»
upload problems
I looked at the raw data of the upload and it looks to me that the duration of the workout was excessively long. Was a workout alive in the background overnight or something like that?
The flaw is that the time offset for each data sample is recorded wrong (and very large). Normally the time step for each sample starts at 1 second; yours starts at 48.5 hrs.
If you have more insight as to how that might have come about, I might be able to reproduce and correct for this in the future.
Probably there is nothing you can to to rescue the data.
upload problems
Hi Ransom - thanks for the prompt reply.
I used it on the 3rd when it crashed during a workout - I restarted and used an ad-hoc to complete - this uploaded OK.
Prior to the workout I did on the 5th, I powered off and restarted my phone. I pressed Load+Go to load from the website and start.
Should Load+Go not kill any prior workout? Is there a way I can tell if there is an open workout running?
Cheers
upload problems
If you launched the app and it didn't return to a running workout, then there was no other workout in progress, and in fact the app was completely shut down, as the app does a hard exit when you close it when a workout is not active.
Maybe it was Load+go that was the source of the problem. I'll try to reproduce.
Crashes during a workout suck. Be on the lookout for an update to drop any day now ("In review" for the app store the last few days) That should fix number of crashing bugs as well as some KICKR improvements and an iOS7 UI.
upload problems
OK thanks - I will avoid the Load and go feature for now.
I'm looking forward to the new release.
Thanks again.
M