[iOS] Fix extra bottom space in ScrollView when using SafeAreaEdges

[Tamilarasan-Paranthaman]

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!

Root Cause of the Issue:

• The issue was caused by a race condition between KeyboardAutoManagerScroll and the ScrollView’s SafeAreaEdges.SoftInput logic. The KeyboardAutoManagerScroll executed before the layout adjustments for SafeAreaEdges.SoftInput, resulting in padding being applied without considering the updated safe area values. As a result, extra/unwanted padding was added below the bottom of the ScrollView.

Description of Change

• To resolve this, a consistent 30ms delay is now applied to all input controls within the KeyboardAutoManagerScroll logic. Previously, the delay was applied only when the InputAccessoryView was present. This change ensures that KeyboardAutoManagerScroll executes after layout updates, based on the recalculated layout. As a result, it maintains consistent behavior and prevents conflicts between the scrolling logic and SafeAreaEdges.SoftInput adjustments.

Screenshot

Before Fix	After Fix
Before-Fix.mov	After-Fix.mov

[Copilot]

Pull Request Overview

This PR fixes a race condition in iOS ScrollView that caused extra bottom spacing when using SafeAreaEdges. The issue occurred when KeyboardAutoManagerScroll executed before SafeAreaEdges.SoftInput layout adjustments, leading to incorrect padding calculations.

• Applies a consistent 30ms delay to all input controls in KeyboardAutoManagerScroll
• Ensures proper timing coordination between keyboard auto-scroll and safe area adjustments
• Prevents conflicts that previously caused double padding or incorrect positioning

[PureWeen]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[PureWeen]

GridStarRowScrollingTest is failing

Can you check if the test just needs to be fixed?

[Tamilarasan-Paranthaman]

GridStarRowScrollingTest is failing

Can you check if the test just needs to be fixed?

@PureWeen, this test seems to be failing due to a timing issue. Locally, the Entry sometimes fails to scroll into the correct position when tapped. Slightly increasing the existing delay before requesting the layout to scroll again, after the initial scroll, seems to resolve the issue. Could you please share your thoughts on this?

[PureWeen]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[PureWeen]

• failing tests aren't related

[PureWeen]

/backport to release/10.0.1xx-preview7

[github-actions]

Started backporting to release/10.0.1xx-preview7: https://github.com/dotnet/maui/actions/runs/16751639340