[iOS] Fix SearchBar unexpected left margin in iPad windowed mode on 26 Version

[SubhikshaSf4851]

Note

Are you waiting for the changes in this PR to be merged?
It would be very helpful if you could test the resulting artifacts from this PR and let us know in a comment whether this change resolves your issue. Thank you!

Root Cause :

iPadOS 26 windowed mode introduces a left safe-area inset (due to traffic light buttons). UISearchBar applies this via UIKit, and MAUI also applies safe area at the layout level. Both together cause a double inset, resulting in an extra left margin.

Description of Change :

Safe Area Handling Fix:

• Updated the MauiSearchBar constructor to set InsetsLayoutMarginsFromSafeArea = false, preventing UIKit from automatically applying safe-area insets and avoiding double-inset scenarios on iPadOS 26+ windowed mode.

Testing :

• Added a new test, MauiSearchBarInsetsLayoutMarginsFromSafeAreaIsFalse, to verify that InsetsLayoutMarginsFromSafeArea is disabled on the MauiSearchBar, ensuring the fix remains in place.
• Included the necessary using Microsoft.Maui.Platform; directive in the test file to support the new test.

Issues Fixed

Fixes #34551

Tested the behavior in the following platforms

• Windows
• Android
• iOS
• Mac

Before Issue Fix	After Issue Fix
BeforeFix34551.mov	AfterFix34551.mov

[github-actions]

🚀 Dogfood this PR with:

⚠️ WARNING: Do not do this without first carefully reviewing the code of this PR to satisfy yourself it is safe.

curl -fsSL https://raw.githubusercontent.com/dotnet/maui/main/eng/scripts/get-maui-pr.sh | bash -s -- 34704

Or

• Run remotely in PowerShell:

iex "& { $(irm https://raw.githubusercontent.com/dotnet/maui/main/eng/scripts/get-maui-pr.ps1) } 34704"

[SubhikshaSf4851]

🤖 AI Summary

📊 Expand Full Review — 97fab15 · updated condition only for iPad

As recommended I have moved the logics into MauiSearchBar also Added Device Test

[Copilot]

Pull request overview

Fixes the extra left margin seen on iPadOS 26 in windowed mode by preventing UISearchBar from propagating safe-area insets into its layout margins (avoiding a double-inset when MAUI already applies safe area at the layout level).

Changes:

• Set InsetsLayoutMarginsFromSafeArea = false for MauiSearchBar.
• Add an iOS device test asserting MauiSearchBar.InsetsLayoutMarginsFromSafeArea is false.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
src/Core/src/Platform/iOS/MauiSearchBar.cs	Disables UIKit’s safe-area-to-layout-margins propagation on the native search bar.
src/Core/tests/DeviceTests/Handlers/SearchBar/SearchBarHandlerTests.iOS.cs	Adds a regression test asserting the new default value for InsetsLayoutMarginsFromSafeArea.

[kubaflo]

The tests failed

[SubhikshaSf4851]

@kubaflo I have checked the device tests and UI tests in local which contains category searchBar and no test were failed. I have also checked the test for issue34551, It fails without Fix and passed with Fix.

WithOut Fix	With Fix

Device Test	UI Test

[kubaflo]

There'a an updated ai's summary - could you please check it?

[SubhikshaSf4851]

@kubaflo I have implemented the suggested changes

[sheiksyedm]

/azp run maui-pr-uitests , maui-pr-devicetests

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[kubaflo]

The device tests are failing for iPhone 11

[SubhikshaSf4851]

The device tests are failing for iPhone 11

@kubaflo I have checked the test in local iphone 11 simulator in 18 and 26 version. No failures were observed. Also i have checked in device test which contains category SearchBar in iOS, Also no failure were observed.

[sheiksyedm]

/azp run maui-pr-uitests , maui-pr-devicetests

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[kubaflo]

Could you please review the AI's suggestions?

[SubhikshaSf4851]

@kubaflo I have updated the suggested changes ,

[kubaflo]

Maybe we should scope it to iOS 26+ only?

[SubhikshaSf4851]

@kubaflo Initially added a condition and limited the fix to version 26, but the AI summary suggested removing it. However, removing the condition did not change the behavior in version 18. so kept it as it is.