Nick on 01 Nov, 2015 11:01 PM
there is a fix waiting for review.
Really sorry. In the mean time - please turn off ‘Allow Auto-Lock’ in settings and keep Kinetic in the foreground (battery life will be reduced). Don’t think Auto Lock is strictly necessary (i.e. screen can sleep), as we tested before release, but it does seem if app is not foremost, then this happens...
Or, If you would like a fix before Apple get around to approving it, you can sign up to be a beta tester? Please provide your apple iTunes email if so, and we can add you.
Kinetic has fouled up 2 runs for me now. One of them was the first run I did with my wife, what fanastic timing that was for a complete meltdown in the app. If I don't hear the kilometer announcement when I expect it then I have to stop to mess around with the app and that it my run screwed up around kilometre run. I pushed on for another 1/2 k or so and it appears that the latest release is recording miles as kilometres. So I would have to run 5 miles to record 5km. After the last foul-up I restarted the phone in case that was the problem, nope, another run screwed.
I have been using Kinetic since January 2014 for walking and now running. The distances I have covered are a personal record and I use them for motivation. When walking I recorded in imperial units, now I am running I use metric as it is easier to get confirmations every 1km.
Kinetic was in the foreground for part of the run, I don't use auto lock and I am not convinced you know what the problem is. iPhone 6s+ 128GB.
How can you release the software when it doesn't perform its primary function? Did you test it at all? I am really flipping angry about this. I feel betrayed by an app I have recommended to other people.
Exact same situation as Steve mentions above. Not only does Kinetic stop announcing my lap times, it also stops the music I have playing. Why would you release a version of software so flagrantly inept? Does being fast out the door with this crap sandwich of an upgrade really serve your client base? Congratulations on knowing what the issue is. When do you expect to release the fix?
Took the first beta fix, had a footle around in the settings and turned off Auto Lock. (I must also have toggled default units. Went for a run and very happy to hear the first KM voice prompt at the correct distance. Huge relief as I had taken a look at other GPS apps and was not impressed with any of them.
Take the second beta update which fixes startup crashes. Testflight says I am running 1.43 (2263). Go for another run with confidence. Get past the first kilometer no report. Oh **** not again! Stop run to fiddle with the app including pressing STOP. Kinetic thinks I have run .47KM. I fiddled with the distance units convinced that it was recording in miles and reporting them as kilometres. For the rest of the run the kilometer markers came up as expected so I started to write this post convinced I knew the answer.
Looking at the GPS track on Google maps Kinetic only recorded the Data point where I pressed start and then the first stop. So the first part of the run is a direct line between the two points. The rest of the run Kinetic must have stayed in the foreground and recorded the GPS data correctly.
This is simply not acceptable, more data lost by Kinetic. I don't want to have to monitor the app to check it is in the foreground. Anyway you don't have a fix for the reliability issue with the latest beta and probably not the previous one. I run the same route every time. IMG_7569.png is this morning's screw-up, IMG_7570.png is yesterday's correct track for the route.
Nick on 06 Nov, 2015 09:35 AM
Sorry you have lost more data. This looks like Kinetic did not
get a GPS lock before the app was put into the background...
Will look into how this can happen. Thanks for the report...been
working reliably for everyone else.
Please make sure you have a good GPS signal before pressing
start and turning off the screen (i understand this is not ideal -
and will look into, a lot of things changed behaviourally with the
GPS in iOS9 SDK).