I see the same issue for a handful of users.

Apple folks: FB15345379

I’m starting to suspect the issue is related to Apple IDs associated with developer accounts, as that’s the only common factor I’ve identified so far.

I have this issue as well. Has anyone been able to figure this out?

@cecilia_hollins Just following up to see if you were able to package your solution. I’m confident it would be a valuable resource for visionOS developers. Thanks!

I am having this issue as well. In my case, the software keyboard is automatically dismissed event if I add a UIScribbleInteraction to my UITextField

Still experiencing this issue with macOS 15.3 Beta 3 (build 24D5055b). I guess Apple’s focus has shifted to promoting TV shows and generating bogus news summaries, rather than addressing bugs in features that have been part of macOS since its inception 24 years ago. So much for “the modern way to build apps is SwiftUI” slide in a recent WWDC video...

Still not resolved in 15.3RC (24D60). Like the SwiftUI engineers, I’m giving up. I’ll leave it to users who want customizable toolbars to contact Apple instead.

Still not fixed in macOS 15.3 (24D60). FB15513599 import SwiftUI struct ContentView: View { @State private var showEditItem = false var body: some View { VStack { VStack { Text("Instructions to reproduce the crash") .font(.title) .padding() Text(""" 1. Click on "Toggle Item" 2. In the menu go to File > New Window 3. In new window, click on "Toggle Item" """) } .padding() Button { showEditItem.toggle() } label: { Text("Toggle Item") } } .padding() .toolbar(id: "main") { ToolbarItem(id: "new") { Button { } label: { Text("New…") } } if showEditItem { ToolbarItem(id: "edit") { Button { } label: { Text("Edit…") } } } } } }

Still an issue with Xcode Version 16.3 beta 2 (16E5121h) and macOS 15.4 Beta (24E5222f).

Still an issue with Xcode Version 16.3 beta 2 (16E5121h) and macOS 15.4 Beta (24E5222f).

Still an issue with macOS 26 beta 1 (25A5279m) and Xcode 26 beta 1 (17A5241e). At this point I assume this will never get fixed.

Still an issue with macOS 26 beta 1 (25A5279m) and Xcode 26 beta 1 (17A5241e). At this point I assume this will never get fixed.

Same issue here.

Same issue. Have you been able to find a solution?