They'll either release nothing, or it'll be dog crap like their predictive code completion that most of the people I know uninstalled...

Xcode 16.3 and still no Swift Assist. WWDC25 is around the corner....

not happening if you build the project in xcode 15.4. I currently have xcode cloud setup to build in 15.4 until they fix this bug(hopefully in xcode 16.1)...

I'm building in xcode 15.4 until they fix this.

Clearly it's not fixed. How is this the accepted answer?

Did you submit feedback?

I have no issues when I build in Xcode 15.4, as soon as I build in Xcode16 I face the same issue.

that might be swiftdata/coredata if you're using those. It can be anything basically...

@malc "View struct hierarchy with its dependency tracking and diffing is the view model already" what if I work on an iPhone, iPad, and MacOS app? 3 different UIs and the same business logic? With MVVM I'd have 3 different Views that share the same VM. How would I achieve that with MV(or whatever it is) approach? Also how do you unit test your logic if it's inside a View?

Except you cannot access environment objects inside your view model, store, or however you wanna call it...

I have a single Hashable enum & a single .navigationDestination for routes and it's still crashing.

Isn't your StoreModel still a ViewModel just named differently though?

this doesn't work. tested on ios16+