Update: I noticed that handleActiveWorkoutRecovery won't be called after relaunch, but I was able to successfully restore the session by calling recoverActiveWorkoutSession in applicationDidFinishLaunching.
func applicationDidFinishLaunching() {
HKHealthStore().recoverActiveWorkoutSession(completion: { session, _ in
guard let session = session else {
return
}
WorkoutManager.instance.recover(session: session)
})
}
jbrunhuber
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
I solved this problem by providing the NSLocationWhenInUseUsageDescription key in the Info.plist of the iOS app (Additionally to the WatchKit extension). The iOS App never tracks location and therefore it never asks for permission, but it seems like the keys are still necessary.
Hi, I filed a feedback (FB13195525) and the resolution is "Potential fix identified - For a future OS update". Guess we have to wait a bit, but Apple is definitely on it.
Update: I updated to macOS Sonoma RC2 and Simulator performance seems to be normal again.