watchOS app fails to launch after Xcode 14 merges App & Extension targets

Question

Created Jul ’22

Replies 2

Boosts 0

Views 1.1k

Participants 3

New in Xcode 14, Xcode will attempt (with your permission) to merge your watchOS targets into a single target. Since the beginning, watchOS apps always had an App Target and an Extension Target. I believe this is from legacy watchOS 1 where the code would run on the iPhone but the assets would run off the watch.

Anyway, in Xcode 14, there is now a way to combine these into a single target.

In Xcode 14 Beta 3, I attempted to let Xcode 14 do this migration for me to the single-target and while no issues happened, my app on watchOS now fails to launch.

It points to a crash on @main on my ExtensionDelegate class.

There isn't much in the debugger other than: Couldn't instantiate class _TtC30PDX_Transit_WatchKit_Extension23MainInterfaceController

Any ideas of where I can begin with this?

Boost

Answer 1

jonas_man OP

Jul ’22

In here, the app never run and xcode just throws errors. Tried to modify the build settings and info plist but no success.

0

Answer 2

Frameworks Engineer OP

Apple

Aug ’22

You should not have an ExtensionDelegate anymore after migrating to a single-target Watch app (because there's no longer an Extension target). You should have an app delegate instead. If your code looks correct, try quitting Xcode, deleting Derived Data and, and relaunching.

0