MAUI iOS: Keyboard hides the entry on iOS platform.

Question

MAUI iOS: Keyboard hides the entry on iOS platform.

Sreenivasan, Sreejith 1,025

I have and entry like below:

<ctrl:BorderLessEntry x:Name="_borderlessEntry" Text="{Binding Text, Source={x:Reference this_flow_text}}" 
                   BackgroundColor="Transparent" Placeholder="{Binding Title, Source={x:Reference this_flow_text}}"
                   Style="{Binding TextStyle, Source={x:Reference this_flow_text}}" 
                   Keyboard="{Binding Keyboard, Source={x:Reference this_flow_text}}">
                <ctrl:BorderLessEntry.Margin>
                    <OnPlatform x:TypeArguments="Thickness">
                        <On Platform="iOS" Value="10,0,20,0" />
                        <On Platform="Android, WinPhone, Windows" Value="10,0" />
                    </OnPlatform>
                </ctrl:BorderLessEntry.Margin>
            </ctrl:BorderLessEntry>

When I tap on it the keyboard hides the entry on iOS platform. I tried couple of workarounds to fix it, but nothing works so far.

Below is its full XAML code: Here FlowFieldGroup is a ContentView.

<?xml version="1.0" encoding="UTF-8"?>
<ctrl:FlowFieldGroup 
    xmlns="http://schemas.microsoft.com/dotnet/2021/maui"
    xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml" 
    xmlns:ctrl="clr-namespace:Xamarin.Forms.Clinical6.UI.Controls" 
    x:Class="Xamarin.Forms.Clinical6.UI.Controls.FlowFieldText"
    x:Name="this_flow_text">
    <ctrl:FlowFieldGroup.Editor>
        <Grid VerticalOptions="FillAndExpand" Margin="10,10,10,0" Padding="0" HorizontalOptions="FillAndExpand">
            <Grid.RowDefinitions>
                <RowDefinition Height="50" />
                <RowDefinition Height="Auto" />
            </Grid.RowDefinitions>
            <Frame x:Name="_backgroundFrame" Grid.Row="0" VerticalOptions="FillAndExpand" HorizontalOptions="FillAndExpand" 
                   BackgroundColor="White" HasShadow="false" BorderColor="#B8B8B8" CornerRadius="3">
            </Frame>
            <Label Grid.Row="0" Text="{Binding TitleHolder, Source={x:Reference this_flow_text}}" 
                   Style="{StaticResource flowText}" Margin="10,-8,0,0"
                   IsVisible="false" x:Name="_holderTitleLabel"
                   FontSize="12" BackgroundColor="White" HeightRequest="15"
                   HorizontalOptions="Start" VerticalOptions="Start">
            </Label>
            <ctrl:BorderLessEntry x:Name="_borderlessEntry" Text="{Binding Text, Source={x:Reference this_flow_text}}" 
                   BackgroundColor="Transparent" Placeholder="{Binding Title, Source={x:Reference this_flow_text}}"
                   Style="{Binding TextStyle, Source={x:Reference this_flow_text}}" 
                   Keyboard="{Binding Keyboard, Source={x:Reference this_flow_text}}">
                <ctrl:BorderLessEntry.Margin>
                    <OnPlatform x:TypeArguments="Thickness">
                        <On Platform="iOS" Value="10,0,20,0" />
                        <On Platform="Android, WinPhone, Windows" Value="10,0" />
                    </OnPlatform>
                </ctrl:BorderLessEntry.Margin>
            </ctrl:BorderLessEntry>

            <Label VerticalOptions="Start" Grid.Row="1"
                   HorizontalOptions="StartAndExpand" Margin="2,0,0,0"
                   Style="{StaticResource loginTextThird}"  
                   HorizontalTextAlignment="Start" x:Name="_errorLabel"
                   TextColor="{StaticResource ErrorTextColor}" IsVisible="false" />
        </Grid>
    </ctrl:FlowFieldGroup.Editor>
</ctrl:FlowFieldGroup>

Let me know what other details you need to debug this issue?

0 comments

2 answers

Your answer

Answer 1

Nguyen Dam (WICLOUD CORPORATION) 160 Microsoft External Staff Moderator

Hello @Sreenivasan, Sreejith , and thank you for providing the XAML code.

We understand how disruptive this keyboard behavior can be, and we appreciate your patience while we narrow down the cause. Since the behavior may depend on both the control implementation and its containing page layout, we would like to better understand how the control is positioned and handled within the complete page. This will help us identify the source of the behavior and focus the investigation on the appropriate area.

Please provide the complete containing page layout where the control is used (including all parent containers up to the ContentPage), and we can investigate the behavior further. In particular, we need to see:

Where FlowFieldText is positioned on the page
Whether it is inside a ScrollView or another scrollable container
Whether the issue occurs in portrait, landscape, or both
Whether other content prevents the page from moving when the keyboard opens
Any code that moves or scrolls the field when it receives focus

Hope the answer is helpful enough for you. And if it is any helpful, please consider following the guidance to provide feedback.

Sreenivasan, Sreejith 1,025 Reputation points

2026-09-08T10:07:39.2533333+00:00
@Nguyen Dam (WICLOUD CORPORATION) Thanks for your response.

Where FlowFieldText is positioned on the page

Almost bottom of the page.

Whether it is inside a ScrollView or another scrollable container

I can't find its origin, I tried adding focused event like below and where I print the value of parent and it is a stacklayout. (Microsoft.Maui.Controls.StackLayout)

private async void OnEntryFocused(object sender, FocusEventArgs e) { await Task.Delay(300); // Wait for keyboard animation var parent = this.Parent; Debug.WriteLine("parent:>>"+parent); while (parent != null) { if (parent is ScrollView scrollView) { await scrollView.ScrollToAsync(0, double.MaxValue, true); break; } parent = parent.Parent; } }

Whether the issue occurs in portrait, landscape, or both

I check it on portrait mode only

Whether other content prevents the page from moving when the keyboard opens

The other contents are able to scroll when keyboard appears. But there are scrolls in inner part and outer part separately

Any code that moves or scrolls the field when it receives focus

Initially no codes, I tried like above, but no luck.

Could you start a one to one message, I can share some other details over there.
Nguyen Dam (WICLOUD CORPORATION) 160 Reputation points Microsoft External Staff Moderator

2026-09-09T09:22:17.01+00:00

@Sreenivasan, Sreejith Sorry for the delay in response. And yes, we can start a one to one message. I will try to help you troubleshoot the issue there. Here are a few things I'd suggest trying:

• Replace the custom BorderLessEntry with a standard MAUI Entry and see whether the issue still occurs.

• Move the affected FlowFieldText higher up on the page and test again. If the problem only happens near the bottom, that would point more toward keyboard/layout behavior.

• Temporarily hide the bottom footer section (the row containing the Continue button) and check whether the Entry is still covered by the keyboard.

• Since FlowFieldPicker seems to behave differently, try placing one in the same position as the affected FlowFieldText and compare the results.

Based on the files shared so far, my current suspicion is that this may be related to the iOS keyboard interacting with the page layout (possibly the nested scrolling structure and fixed footer) rather than the Entry control itself.

Let me know if any of the above changes the behavior.

Answer 2

On iOS, Entry fields are expected to scroll into view automatically when the soft keyboard would cover them. In .NET MAUI, pages automatically scroll so the text field stays above the keyboard.

For this layout, the most relevant fixes are:

Put the input inside a keyboard-aware container.
- Set SafeAreaEdges="All" on the page or wrapping layout if the whole page should avoid system bars and the keyboard.
- For bottom input layouts, wrap the content in a layout such as Grid or VerticalStackLayout and set SafeAreaEdges="SoftInput" or SafeAreaEdges="All" on that wrapper.
- Do not set SoftInput directly on a ScrollView, because it does not work there.
If this ContentView is hosted near the bottom of the screen, make sure its parent page or parent layout handles keyboard avoidance, not just the Entry itself.
- A control-level margin such as OnPlatform margin will not solve keyboard overlap by itself.
Check whether iOS keyboard auto-scrolling was disabled in app code.
- If KeyboardAutoManagerScroll.Disconnect was called anywhere, the default iOS behavior is disabled.
- Re-enable it with KeyboardAutoManagerScroll.Connect after the code path that disabled it.
Use valid MAUI platform names in OnPlatform.
- WinUI is the correct Windows platform value.
- Windows is not the documented value.

Example of a keyboard-aware wrapper:

<ContentPage SafeAreaEdges="All">
    <Grid>
        <!-- existing content -->
    </Grid>
</ContentPage>

Or for a nested layout that should specifically avoid keyboard overlap:

<Grid SafeAreaEdges="SoftInput">
    <!-- FlowFieldGroup / Entry content -->
</Grid>

If the page already uses a ScrollView, wrap that ScrollView in a Grid and apply SafeAreaEdges to the Grid, not the ScrollView.

Also note that the documented Entry behavior on iOS is automatic keyboard avoidance, so if this still fails after moving the control into a keyboard-aware parent and ensuring KeyboardAutoManagerScroll was not disconnected, the issue is likely in the surrounding page layout rather than in the Entry XAML itself.

References: