There was no announcement of a new version this year. If I'm mistaken, please send me a link, where anything about a new version was said.

There is some kind of backport https://www.pointfree.co/blog/posts/129-perception-a-back-port-of-observable of the Observation API to earlier system versions by some very awesome guys. Perhaps look into that.

Sorry, perhaps I misunderstood your code, but the old Observable API is known for not updating if model classes are nested. The new Observation API is better to detect changes in classes nested more than one level deep.

Sorry, may not be the solution you asked for, because it is for NSDataAssets, not Data itself.

unfortunately this links to itself. Did you mean: https://developer.apple.com/forums/thread/742177

You don't have to do anything in your code. You only have tell Xcode to include the file in your project. Unfortunately I don't have the necessary steps available here today. But have you tried it already?

For an explanation see https://levelup.gitconnected.com/state-vs-stateobject-vs-observedobject-vs-environmentobject-in-swiftui-81e2913d63f9 and https://www.hackingwithswift.com/quick-start/swiftui/understanding-property-wrappers-in-swift-and-swiftui

PS: It would be really helpful to state something like the map workaround in the documentation of .notifications(named:...). The literature about swift concurrency is still very sparse and though there are millions of blog entries explaining async await syntax and the simplest patterns there is still much missing when it comes to best practises and tricks like that above.

Thank you, your answer was very helpful because it explained the reason for the warnings and gave a reasonable workaround which was not obvious for me!

I'm glad, that I could help. Could you please mark the answer as „correct ✅“, if you feel this way?

This should work, but there should also be an easier way. Come on Apple!

In this WWDC Video the reverse case is shown: NavigationStack inside of NavigationSplitView. Still hoping both cases will be supported in later betas.

The beta last year, was not available for all developer program members. This spring there was a more public beta. Let's hope it will be available for a larger group again, later this summer.

The Question was „Why LazyHStack takes full height but HStack does not?“. I thought I answered that. What did I do wrong?

You are of course right! This one-liner even confused me, though I used many computed vars in Swift already. ;-)