As mentioned by developper 555 migrating watch app to a single target fixed the issue :) THANKS !

You can update the recommendations by calling: WidgetCenter.shared.invalidateConfigurationRecommendations()

just reuse the add review option you can then edit your original text

Have a look at UISearchBar https://developer.apple.com/documentation/uikit/uisearchbar

I’d try with the latest beta, Xcode 15 Beta 8

No, butI will do it tomorrow morning Hopefully we can get this fixed before the official release … thanks

Sounds weird, I have no issue to get more than 10 complications descriptors that are all listed in the complication selection screen When the number of descriptor is dynamic, you should ask the complication server to reload the descriptors as follow: let complicationServer = CLKComplicationServer.sharedInstance() complicationServer.reloadComplicationDescriptors()

Thank you jcgoforth, the 'defaultMyThingForMyIntent:' is indeed the right place. Thanks !

I had the same issue, I fixed by adding the NSUserActivityTypes key to the main app Info.plist file with the DynamicIntent name

I have the same issue ... I've spent hours on it, tried to set the default values in different places: in the Provider struct: in func placeholder(in context: Context), let configuration = SelectDataItemIntent() configuration.dynamicParam = [DynamicParam], size depending on context.family in func getSnapshot(for configuration:  if configuration.myDynamicParam == nil { ... } in func getTimeline(for configuration: if configuration.myDynamicParam == nil { ... } That works fine for the preview and for the widget itself, but unfortunately the set parameters as not saved. Therefore the EditWidget UI shows 'select' for each parameter instead of the expected value .. not very nice ... I've also tried to initialize it in the Widget struct, but the Intent configuration requires an instance type of the Intent, not an actual instance, so it seems not possible from there... Have you find any solution ?

The shared complication server CLKComplicationServer.sharedInstance() is always accessible. It seems the .activeComplications is initialized only after WKExtensionDelegate.applicationDidFinishLaunching (or in parallel to ?) So yes it can be nil if you try to use it before its initialization.