Another interesting clue. At one point, I tried using a loaded image as my complication before I turned it into a system image because I couldn't load the images from my asset catalogue. I'm starting to wonder if some of the widget default directory setups are now different from what I have in this old Objective-C project. It can't find this stuff because it's looking in a place that doesn't exist.

Another thing I noticed after looking at the download Apple app is that it has a Watchkit App and a widget and no Watchkit Extension. Don't know if that matters or not.

Changed the bundle name of my apps watchkit App and that changed the name of the app in the iPhone water app. I guess this boils down to my Cfbundledisplayname entries being ignored Or overridden.

Changed the watch app display name and it changed the complication app name in the iPhone watch app as expected. Simply added two Xs to the end and the Xs immediately showed up in the iPhone watch app.

Downloaded and installed the app and the app name looks good. Now one difference is that my app is a combined objective-c but the widget is in swift. My widget looks pretty much like the one here. I'm going to change some of the bundle identifier display names around and see what I get.

MacOS - 15.3.2 Xcode - 16.3 IPhone - 18.3.2 WatchOS - 11.3.1 These are all fairly up to date.

I should have clarified this post a little. I was able to do that for MacOS and iOS projects but I was trying to make a new WatchOS project and that did not have an objective-c option. I guess I could just use Xcode 14.(whatever) to generate the project and bring it into Xcode 15 but that seems kind of silly. I have current watchOS obj-c projects and everything works ok in Xcode 15 except when debugging code on the watch itself (not simulator) console panel shows a direct LLDB interface.

Well seems to work ok for iOS projects and MacOS projects but I'm trying to create a watchOS project and that option doesn't exist there. Maybe I'm still missing something.

It kinda magically cured itself. I think something needed to be approved and maybe that took some time even though the app was already in TestFlight? I opened a TSR and suddenly all was ok.