I built a workout app for watchOS. After finishing the workout, I'm noticing that the system repeatedly pushes the app to the foreground, even if I push the app to the background after the workout. It is unclear why this is happening.
I followed Build a workout app for Apple Watch and I correctly finish the workout as far as I'm aware, with no errors being throw by the system or HealthKit.
What could be causing this behavior? In other words, in what scenario does the system push an app to the foreground (after completing a workout)?
Note that I'm not using WorkoutKit, just HealthKit.
I tested this on a physical device, Apple Watch Series 8, running watchOS 9.6.
bartjacobs
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
The tvOS and watchOS platforms aren't installed by default using Xcode 14. This poses a problem for continuous integration if Xcode was installed with only the default platforms (iOS and macOS). Is it possible to install additional platforms through the command line?
The NSCollectionLayoutContainer protocol defines contentSize and effectiveContentSize. There's currently no documentation available for this protocol (and most of the compositional layout API). What is the difference between contentSize and effectiveContentSize and contentInsets and effectiveContentInsets?