So this is an odd one. I just pushed a build from Xcode 14 for testing and installing that build on iOS 15 causes the app's home screen widgets to disappear. My app is no longer listed when I go to add a widget. If I run it on iOS 16 everything works fine. If I run it from Xcode 14 to a simulator running iOS 15 everything is fine. What is happening is on a true iOS 15 device it is failing to find a symbol in the WidgetKit framework. Here is the output: Symbol not found: _$s9WidgetKit22IntentTimelineProviderPAAE15recommendationsSayAA0C14RecommendationVy0C0QzGGyF Referenced from: /private/var/containers/Bundle/Application/8B7C4700-E1FD-4174-BD13-B51FBA121B3D/WeatherViewer.app/PlugIns/WeatherWidgetExtension.appex/WeatherWidgetExtension Expected in: /System/Library/Frameworks/WidgetKit.framework/WidgetKit From what I understand the new "recommendation" method is not needed on iOS and is meant for WatchOS. I have this new method implemented and it's only @available(iOSApplicationExtension 16.0, *) so not sure why it's being called. Even if I remove it completely and try a new build it still has the WidgetKit crash. Any help would be appreciated. I would love to get this back working and not have to rollback and ditch my iOS 16 additions.

I have one user that is getting some very odd behavior for one of my complications. The complication will work fine for a little bit, but then gets into a state where when the watch is asleep it is displaying correctly and then when the watch wakes up it's the default dashed out view with the app name. This is happening on a Watch Series 5 with cellular that is on the latest WatchOS (8.5). It was also happening on 8.4.2. All of the other complication types work perfectly fine on their watch. It is just this specific one, which other than the way the view is laid out is no different than the others under the hood. They all share the same data. The problem complication uses CLKComplicationTemplateGraphicRectangularFullView and the only thing I can think of is that maybe there is an issue with support on the Series 5. Though I have no evidence to support this theory since there isn't any helpful log messages. Testers on Series 6 and Series 7 report zero problems with this complication. I have added in a special view for when this complication fails for whatever reason, at least whatever reason I can capture and it is never displayed. It just shows the generic Apple dashed out view. So it seems something else is going wrong under the hood. Any and all help would be much appreciated.

I'm having an issue where the complications for my app aren't syncing to the watch if you add them from the Watch app on iOS. However if you add them from the watch itself they work on the watch, but don't show on the iOS Watch app. I'm using getLocalizableSampleTemplate(for:withHandler:) to generate the complication templates. I'm not including a complication bundle or static images since it appears that this is not needed anymore according to the docs. The templates show fine on both the watch and iOS Watch app, they just don't show up on the watch if added from the iOS Watch app and vice versa. If I add a new watch face and then add the complications to it and try to set it as the default watch face from the iOS app it will set it on the watch, but doesn't have any of the complications. If I load up the Console app and look at the iPhone system logs I can see it trying to send the watch face with the correct complication descriptors, but nothing happens on the watch itself. If I use a simulator it doesn't even sync any of the watch faces until I reboot the watch sim. One final note, the watch portion of the app has not been released in the App store before. This is a new addition to an already released app. Not sure if that could be part of the issue, but just thought I should include it. I'm at a loss here, any help would be appreciated.

If I run our custom intent extension via Siri on WatchOS 7, Siri will not speak or display the intent's response. WatchOS Siri simply responds with: "Done" "That's done" "OK" Meanwhile Siri on iOS responds with our custom intent's response. Oddly enough if I create a custom shortcut based on our app intent and add a step to "speak text" she will then say the response on WatchOS. There seems to be a disconnect between the behavior of shortcuts on WatchOS and iOS. It seems like WatchOS Siri does not read/display custom intent extension responses while iOS does. I thought it might have something to do with our Intent, however even adding a simple Intent Extension that just returns a hard-coded phrase in the response causes the same thing to happen. Am I missing something? Does WatchOS Siri not receive the response other than if it was a success/failure when running the shortcut remotely? Would bundling the Intent with a watch app cause Siri to actually speak the response like I expect?