When completing a workout, why does it take so long to save? Apple Workouts is instant, but YR sometimes takes a minute or two and I get nervous I am going to lose my workout.
The 'this week' and 'this month' complications both show this week.It's also a mystery for me ...
I use the normal API to save data at the end of the workout.
My guess:
- Apple stores less GPS points for the same workout
- Apple has some private APIs that perform incremental saves during the workout
I am also doing some "backup" tasks in case of HealthKit failure. Apple doesn't do that, but it doesn't cost a lot.
If you do interval training, the new way to do it internally is to divide the workout into separate activities, and it's way longer to save at the end. I have seen that another workout app developer has raised the same issue on Stackoverflow.
I have a question for people who have installed the last release: are the Watch complications working ?
It's also a mystery for me ...
I use the normal API to save data at the end of the workout.
My guess:
- Apple stores less GPS points for the same workout
- Apple has some private APIs that perform incremental saves during the workout
I am also doing some "backup" tasks in case of HealthKit failure. Apple doesn't do that, but it doesn't cost a lot.
If you do interval training, the new way to do it internally is to divide the workout into separate activities, and it's way longer to save at the end. I have seen that another workout app developer has raised the same issue on Stackoverflow.
I have a question for people who have installed the last release: are the Watch complications working ?
Thanks for the suggestion, as English is not my native language, there are probably a lot fo similar mistakes.Another minor observation regarding voice alerts. I think this is just a translation issue, but when using intervals, the voiceovers at the start of an internal are not quite right.
Example
'Recovery during 500 meters' should be 'Recover for 500 meters'
'Work during 500 meters' should be 'Work for 500 meters'
Notice recover instead of recovery and for instead of during. Hope this helps.
I use Coredata as backup while running. It's super fast, the issue is not there.I have an app in the App Store that acts like a bike computer.. It got Sherlocked with the last iOS release.. Anyhow, this is on iPhone.. But, using CoreData, if you record a record say each second, there is no lag or wait time at the end.
I was also for a while recording using CloudKit, which records to iCloud live in realtime.. But that absolutely crushes battery on an iPhone. I opened a ticket with Apple and they told me that's expected.. I was better off storing to CloudKit at the end only.
My suggestion then would be to use CoreData and store a record each second. I had a Timer running and every second, whatever was in the buffer got recorded. Zero wait time at the end of the ride and I didn't notice any change in battery performance.
That was it !Edit:
Could you check if « advanced screen » is ON in settings of the watch app.
If it’s off, you won’t see race and plans as these activities require the second screen to be useful.