We are seeing the same error message as @marioguzman. Info.plist contains WKApplication key entry set to YES in addition we have the Info.plist from the WatchExtension where the WKExtensionDelegateClassName is set with the value set to $(PRODUCT_MODULE_NAME).ExtensionDelegate.
The ExtensionDelegate looks as follows:
import SwiftUI
// ScenePhase observation doesn't work reliably
// https://developer.apple.com/forums/thread/650632
// Implement custom appDelegate and notiy about lifecycle changes
@main
class ExtensionDelegate: NSObject, WKApplicationDelegate {
func applicationWillEnterForeground() {
NotificationCenter.default.post(name: Notification.Name.willEnterForeground, object: nil, userInfo: nil)
}
func applicationDidEnterBackground() {
NotificationCenter.default.post(name: Notification.Name.didEnterBackground, object: nil, userInfo: nil)
}
}
And the watch app crashes at the @main with
Watch[71777:6577905] [default] -[SPRemoteInterface createViewController:className:properties:contextID:info:gestureDescriptions:clientIdentifier:interfaceControllerCreationCompletion:]:3230: Critical failure. Simulating crash: Condition failed:"NO". Couldn't instantiate class _TtC15Watch_Extension17HostingController
Martin@PACE
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
Post
Replies
Boosts
Views
Activity
Just to add to this, because I ran into this problem as well: I think the bundle-identifier property was not verified at all prior to iOS 16. We defined an identifier that was completely different and installation still worked. Good to know that with iOS 16 it has to be exact though.
In our case Xcode lost the session after an Xcode upgrade. Solution was to sign in again in the Xcode preferences on our runners.
@liazkam That is great to know, thanks!