Thanks for your update. Related to this is still that clarity on if I need to implement @WKExtensionDelegateAdaptor I guess you meant WKApplicationDelegateAdaptor by WKExtensionDelegateAdaptor, assuming that your watchOS app is a single-target app? (See TN3157 for the defintion of the term.) In theory, based on the documentation, if you added backgroundTask(_:action:) in your SwiftUI app, you wouldn't need to implement the app delegate’s handle(_:), and hence wouldn't need to implement @WKApplicationDelegateAdaptor (unless you still need something that the SwiftUI app life cycle doesn't provide). In practice, I am actually curious if adding @WKApplicationDelegateAdaptor + implementing the app delegate’s handle(_:) to complete all the background tasks helps avoid the watchdog termination in any way – If yes, there will be a bug related to backgroundTask(_:action:). Maybe you can give it a try, given that you have the test environment? Then there's the 4 updates per hour with a complication on
Topic:
App & System Services
SubTopic:
Health & Fitness
Tags: