@DTS Engineer That is a workaround that might be enough for some, but I would still want to see the actual SwiftUI toolbar API with placement .keyboard to work correctly. The toolbar API includes the liquid glass style toolbar buttons and makes it easy to group related buttons in shared button capsules. I reported this issue well over a year ago in August 2025 (FB19279023) and it still hasn't been fixed.

@DTS Engineer Just want to bump this issue since it doesn't seem like Apple has understood the severity of it. This is probably affecting thousands of apps, and has been a problem since the first iOS 26 beta last summer. This used to work in iOS 18, so it's even a regression. My feedback from August last year: FB19601591

Still an issue in iOS 26 RC, will need to revert to the old transition style. I really hope this will be fixed in iOS 26.1....

This is still not working in iOS 26 beta 9. I will probably need to revert to the old transition style unless it's fixed in the Release candidate.

I have seen similar issues in my app. If a button is disabled the text disappears, and expand indicators are not visible. In Light Mode everything works fine. FB19069393

Ah thanks I missed that in the release notes. Using the workaround the largeTitle doesn't work which is a bummer. Hopefully toolbarForegroundStyle gets fixed before release.

I noticed this too, must be a bug in beta 1. I have reported it in feedback assistant FB18056069.

I also had a hard time figuring this out, but finally found it. In addition to having the .searchhable view modifier, you also need to put a search toolbar item in your toolbar, like this: DefaultToolbarItem(kind: .search, placement: .bottomBar)

I found this post by a SwiftUI engineer describing the issue, what's causing it and how to fix it. https://hachyderm.io/@teissler/112533860374716961 Basically, if the view in the navigationDestination references any property in the presenting view, it will capture self and all its properties. This is a problem if you have environment values that are not Equatable (like \.dismiss) and will cause a SwiftUI cycle that freezes the app. The solution is to use a capture list in the navigationDestination closure to only capture the properties that are needed to construct the presented view. Also, if you have custom environment values, make them Equatable whenever possible to avoid this issue.