On iOS 27 beta, when a search field hosted by a UISearchTab becomes active in landscape on a device with a sensor housing, the field lays out edge-to-edge, and its leading magnifier ends up inside the safe area inset. The same code is correct on iOS 26, so this looks like a regression.
It then gives the environment, the setup (tabs API + UISearchTab with automaticallyActivatesSearch, plain UISearchController assigned in init, no placement or scrolling flags, no custom bar subclass), expected versus actual, and the measurements:
- window = 812 x 375, safeAreaInsets left/right 50 (usable 50…762)
- tab-hosted, active: field = (8.0, 122.0, 744.0, 44.0) ← 42pt inside the left inset
- tab-hosted, idle: field = (94.0, 311.0, 680.0, 44.0) ← trailing edge overruns by 12pt
- presented (no tabs): field = (101.7, 126.7, 553.0, 30.7) ← fully inside
Not sure if it's known/has a supported workaround.