I have made sure that this line is included in the project.pbxproj for the Release configuration, but when uploading an archive using Xcode 16.1 to App Store Connect for TestFlight internal testing, I get the same warnings reported by @MojoTouch

The Food Truck sample app is a good starting point, but I think the documentation for passkeys should cover the SwiftUI implementation as well.

I agree. It's very basic and lacks many expected experiences like double-click and right-click support and keyboard interactions as well as resize columns to fit column content by double-clicking the column separator. I submitted feedback about it FB10007155. It's really basic and I expect a lot of new features added to it in the next iterations of SwiftUI for it to be production ready.

No I don't think the order of variables matters here. I think the key takeaway from the accepted answer is to add the .searchable(text:) modifier to a parent view, then read the isSearching environment variable from inside a child view (SearchableView in the accepted answer example.)

As of Xcode 13.3 and testing on an iOS 15.4 simulator. This keyboard onboarding screen that covers the keyboard when it is presented for the first time on every fresh install of iOS (or every time I choose Device > Erase All Content and Settings… from the Simulator app) does not count as an interruption by the XCTest framework and does not trigger a call to the interruption handler closure.

This is the only solution I could find to reliably show/hide the UISearchController instance from the navigation bar as well as clearing its space when hidden. However, I wasn't able to show/hide it with animation. I'm not sure if navigationItem.searchController is animatable.