You should probably raise these issues as bugs in the usual way. They won't really get progressed if they're only posted in these Developer Forums. You need to raise each issue you find separately at https://feedbackassistant.apple.com/ You can post the FB numbers here if you want, so that others can link to them.

Your new example doesn't cause a crash in Xcode 26 beta 3 or Xcode 16.4 on my M1 Max Mac Studio with macOS 15.5. I wonder if it's something else. Are you on macOS 26 beta?

It also crashes in Xcode 16.4 because what you're doing isn't valid. In your second example, line 28 is wrong. HelloView does not have any Bindings in it; it just takes a label parameter, so line 29 passes in element.label. Correct. Line 28 is treating your elements State var as though it's a binding, by adding the $ in front. And you're also adding the $ to the element part towards the end of the line. elements is a State var and element is a var whose label property is being passed into a view that does not have a Binding. This is why Preview crashes. It will compile if line 13 is this instead: @Binding var label: String, but based on what you're doing with label inside HelloView, i.e. you're not changing it, there's no need for it to be a binding var.

You should probably raise this as a bug in the usual way. It won't really get progressed if it's only posted in these Developer Forums. You need to raise each issue you find separately at https://feedbackassistant.apple.com/ You can post the FB numbers here if you want, so that others can link to them. When raising a bug it's important to mention which version of which operating system you've found the issue in, e.g. iOS 18.5, iOS 26 beta 3, or visionOS 26 beta 3 etc.

What happens if you remove the NavigationStack on line 14?

This isn't just an Xcode issue This sometimes happens in other apps, too, when some other background process hasn't finished exiting and the main app (Xcode) just waits for it to finish. As you found, the way to close Xcode is to Force Quit it. That won't do any harm. It likely won't do any harm either if you just leave it - unless you want to shut down your Mac. You probably don't need to raise a bug for this, but you can if you like, at: https://feedbackassistant.apple.com/ and post the FB number here. FYI, you don't need to mention your Mac's serial number, especially for software bugs.

There's no need to create a duplicate post just to make a few changes to your original post. You have one hour to make changes to your original post. If you're outside of that one-hour window and the edits are absolutely necessary, just reply to your own post. Duplicate posts clutter the forums.

Apple Geniuses and in-store service generally cannot work with devices on a beta, so you have to be on a publicly-released version. Go back to visionOS 2 (the latest publicly released version), and make another appointment. There are instructions on how to do this all over the internet, but the general gist is you have to wipe the device and install from scratch.

Not everything in a List has to be the same thing. In one of my apps I have a List that has a HeaderView(), then a ToolbarView() then a set of EventRow() views, which looks pretty similar to your wireframe. Something like this: VStack { List { HeaderView() ToolbarView() ForEach(events.indices, id: \.self) { index in EventRow(events[index]) } } } Everything scrolls vertically within.

The video says they're there when you apply the step parameter. If you're not applying that parameter and the tick marks are there, that suggests a bug.

You should probably raise this as a bug in the usual way. It won't really get progressed if it's only posted in these Developer Forums. You need to raise each issue you find separately at https://feedbackassistant.apple.com/ You can post the FB numbers here if you want, so that others can link to them. Also, after you mention "X" is "(formerly Twitter)" once, you really don't need to keep doing it ;)

This sounds like you've just not designed your code properly. Yes, @Binding is used to represent a @State var from a different component, because they are designed that way. They are very useful, and I can see and understand why they exist. As I suggested in your other similar post, just raise the bugs as you find them. If you raise them, they can get fixed.

What do you mean by: SwiftUI compiler fails to compile and just reports "I'm lost in the weeds", with no indication of what it was last working on, aside from a particular level in a multi-layered nested UI. Have you raised any bugs about it? Perhaps if you explain - in a bug - exactly what the issue is, Apple's developers might be able to make improvements. I raised a bug where I'd renamed a binding variable but forgotten to rename it in one place it was being used, and the compiler said it was unable to compile. Apple's developers fixed it, so when I forget to rename the use of the variable now it fails at that point, so I know where the issue is. If you do the same, these bugs will be fixed. You'll be happier, other developers will be happier, Apple developers will be happier. It's the right thing to do :)

These are the Developer Forums, where developers of third-party apps for Apple's platforms ask each other for hints and tips on coding. These forums are not where Apple's actual developers chat about new features. If you have a suggestion, you should raise it at: https://feedbackassistant.apple.com/

Probably, no one here will know for sure, but your guess is sound. I would put a launch screen in now and just be done with it. They're easy to do, so there's no real reason not to, and it means your app won't crash. Win-win!