Hey,I think i had the same problem.. it worked in XC 11.3.1 and 1.4 beta broke it...Now I'm not a 100% on this but i think it was because i used SwiftPackages by locally importing them to XC (via Drag&Drop, as shown @ WWDC). Now for some reason XC didn't quite get that I wanted to use those local packages INSTEAD of the remote ones so in some projects it kept the remote ones wheras in other targets (SiriKit extension, if that matters) it used the local ones and therefore had two different, yet same packages...So I removed the remote ones in Project Settings > Swift Packages and added the local ones to all my targets again.. Now it works...Hope it helps someone ^^

.* transition(with: view, duration: 2.0) animations: {	//doesn't work	}

I'm having the same problem. As of today (Mar 23), the latest ASC trends are from Mar 19th.

Seems like it's been an issue for some time: https://developer.apple.com/forums/thread/127928 My most recent trends are 5 days old :((

Thanks @Palli_k, I don't know if there's any better/correct way of doing it but using: ZStack { AccessoryWidgetBackground() [...] } .widgetBackground(backgroundView: EmptyView()) At least seems to get rid of the error. While keeping the functionality and UI the same.. I have no idea what Apple was thinking.. even their own API is still wrong, 1w after the public iOS 17 release: https://developer.apple.com/documentation/widgetkit/accessorywidgetbackground If there's any good resource about how .containerBackground is actually supposed to work, please lmk..