I'm getting an internal inconsistency exception (Cannot call setItems:animated: directly on a UINavigationBar managed by a controller.) in a thread with no app code. The stack trace suggests something to do with a context menu, but my app doesn't use any. I'm seeing a lot of crash reports, but I can't repro it myself, and no customers have reported it yet so I only have the stack trace (below) to go from. It sure looks like a problem in UIKitCore. CoreFoundation __exceptionPreprocess libobjc.A.dylib objc_exception_throw CoreFoundation +[NSException raise:format:] UIKitCore -[UINavigationBar setItems:animated:] UIKitCore -[_UINavigationBarVisualProviderModernIOS _popToItem:] UIKitCore -[UIAction _performActionWithSender:] UIKitCore -[UIContextMenuInteraction _contextMenuPresentationController:didSelectMenuLeaf:] UIKitCore -[_UIClickPresentationInteraction _handleDidTransitionToPossibleFromState:context:] UIKitCore -[_UIRapidClickPresentationAssistant dismissWithReason:alongsideActions:completion:] UIKitCore -[_UIRapidClickPresentationAssistant _animateDismissalWithReason:actions:completion:] UIKitCore -[_UIRapidClickPresentationAssistant dismissWithReason:alongsideActions:completion:] UIKitCore stateMachineSpec_block_invoke_4 UIKitCore handleEvent UIKitCore -[_UIClickPresentationInteraction _cancelWithReason:alongsideActions:completion:] UIKitCore -[UIContextMenuInteraction _contextMenuPresentationControllerWantsToBeDismissed:withReason:alongsideActions:completion:] UIKitCore -[_UIContextMenuPresentationController contextMenuView:didSelectElement:] UIKitCore -[_UIContextMenuView _performActionForElement:] UIKitCore -[_UIContextMenuView _handleSelectionForElement:] UIKitCore -[_UIContextMenuView _handleSelectionGesture:] UIKitCore -[UIGestureRecognizerTarget _sendActionWithGestureRecognizer:] UIKitCore _UIGestureRecognizerSendTargetActions UIKitCore _UIGestureRecognizerSendActions UIKitCore -[UIGestureRecognizer _updateGestureForActiveEvents] UIKitCore _UIGestureEnvironmentUpdate UIKitCore -[UIGestureEnvironment _updateForEvent:window:] UIKitCore -[UIWindow sendEvent:] UIKitCore -[UIApplication sendEvent:] UIKitCore __dispatchPreprocessedEventFromEventQueue UIKitCore __processEventQueue UIKitCore __eventFetcherSourceCallback CoreFoundation __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ CoreFoundation __CFRunLoopDoSource0 CoreFoundation __CFRunLoopDoSources0 CoreFoundation __CFRunLoopRun CoreFoundation CFRunLoopRunSpecific GraphicsServices GSEventRunModal UIKitCore -[UIApplication _run] UIKitCore UIApplicationMain

I added a watch app to my existing iOS app project using the instructions found here. After adding the new watch target, and doing literally nothing else, my app now fails to build because automatic signing is failing. As instructed, I filed a bug report with the requested information, but the issue was resolved as "Investigation complete - Unable to diagnose with current information". I added a comment offering full access to my source code so they could reproduce the problem. No response... I've tried switching to manual signing, but couldn't get that to work either. I don't understand why they asked me to file a bug report but then refuse to follow through when provided with all of the information they requested (and more)!

Until recently, I was able to debug my watch app and complication, but now Xcode reports "Could not locate installed application" when I try to debug. The watch app is definitely installing correctly, because I can see the app behavior change when I make an update and then attempt to launch the debugger. Also, whenever the app fails to launch, I see a crash log for the DTServiceHub (screenshot is too large to upload here, unfortunately). I'm using automatic signing, and I don't think I've made any significant changes to the app or the project settings. I did upgrade Xcode a couple of days ago (to 13.3.1) and WatchOS (to 8.5.1), so either of those could have introduced the problem. I tried reporting this on the feedback site, but the web site hangs when I try to submit a bug report (on both Safari and Firefox).

I'm trying to debug a problem that's affecting customers who have upgraded to WatchOS 10, and I'm unable to get any console output from the watch when I debug the watch app in Xcode, or from the console app connecting from my Mac. The other weird thing is that my watch shows up twice in the device list in the console app. Is this a known issue?

Prior to (I think) watchOS 10, my navigation title was at the top of the screen, vertically aligned with the time, to its left. At some point (I think in watchOS 10) the navigation title became right-aligned and just below the clock. (I'm hiding the back button). I've tried many variations in my SwiftUI code, but haven't been able to restore the original placement of the navigation title. This messed up the placement of my main content, so I've had to remove the navigation title on many of my app screens. Does anyone know how to place the navigation title in the upper left as it used to be? This is just wasted space now.

I'm trying to use containerBackground to help distinguish between pages in a horizontal TabView, but all of the tab items get the background specified on the first item. I tried using containerBackground in another part of my app that uses a vertical TabView, and it works perfectly there. Does this just not work for horizontal tabs? That seems weird.

I have an iPhone app, and added watch support, including a simple launcher complication. I can add the complication using the edit UI on the watch, but the complication is not visible using the watch app on the iPhone. When I add my complication on the watch and then open the watch app on the iPhone, the complication slot shows as "Off". What could I be doing wrong?