See Bug Report # FB14781136 within Feedback Assistant @DTS Engineer …It has code, screenshots and log.

import SwiftUI struct ContentView: View { @State private var searchText: String = "" var body: some View { NavigationView { Text("Content goes here") .frame(maxWidth: .infinity, maxHeight: .infinity) } .toolbar { ToolbarItem(placement: .automatic) { TextField("Search...", text: $searchText) .textFieldStyle(RoundedBorderTextFieldStyle()) .frame(width: 200) } } } }

Simplest TEST CASE I could make @DTS Engineer @KMacTexas …Create a new Swift macOS project, go to ContentView.swift file and copy-paste this code below into it… then run it, click the SEARCH FIELD and PRESS TAB to see TUINSRemoteViewController error… Note Quick Look Xcode says: "0xad0bc : +[NSSemiAutonomousRendezvousWindowController addBridgeKeys:]" Xcode Version** 16.0 beta 5 (16A5221g)** macOS Sonoma 14.6.1 (23G93)

For the record, "0xad0bc : +[NSSemiAutonomousRendezvousWindowController addBridgeKeys:]" is the "fault" shown with the Quick Look icon at the bottom in Xcode, in my case, which is triggered by a custom NSTextField in the Toolbar. Every time the focus goes in or out of there, that triggers "CLIENT ERROR: TUINSRemoteViewController does not override -viewServiceDidTerminateWithError: and thus cannot react to catastrophic errors beyond logging them". Can't get rid of it yet. @DTS Engineer

I ran this, then deleted and redownloaded the Xcode > Settings > Platforms > iOS 17.0 …Then building the iOS project took forever but worked fine after that. Before doing this it was just stuck at "28" on build, forever (top right where the "Build Succeded" message appears in Xcode project window). So… Thx for the tip.

Thank-You "bigmouthstks". On a Swedish keyboard, command-shift-7 to comment out code disappeared in Xcode 14.0.1 with no warning, but your comment above about unchecking that brought it back… I would have NEVER found this on my own. Apple, please NEVER EVER EVER mess with our key bindings in Xcode again. Seriously. You gonna change that, you better ASK us IF WE ALLOW THAT. After 20 years using Xcode, no-way-this-is-OK. Thank-goodness folks come up with answers who-knows-how.

You are a genius! =) Thanks!