Skip to content

Android TabbedPage inside Modal Navigation does not overlay BottomNavigationView after PushAsync in .NET MAUI 10.0.60 #35331

Description

@tranhoangnam16705

Description

After updating to .NET MAUI 10.0.60, Android behavior changed when using:

NavigationPage
TabbedPage with Bottom tabs
PushModalAsync
PushAsync inside modal flow

Previously, pages pushed inside the modal TabbedPage navigation stack could overlay the entire screen and hide the BottomNavigationView automatically.

After updating to 10.0.60, pushed pages are rendered only inside the fragment content container and no longer overlay the BottomNavigationView.

This issue only occurs on Android.

iOS still behaves correctly.

Steps to Reproduce

Expected Behavior

When using:

await Navigation.PushModalAsync(
new NavigationPage(new MyTabbedPage())
);

and later:

await Navigation.PushAsync(new DetailPage());

the pushed page should fully cover the screen and hide the BottomNavigationView automatically.

Behavior should be consistent with previous MAUI versions and iOS.

Actual Behavior
DetailPage is pushed successfully
Navigation stack works
But BottomNavigationView remains visible
The pushed page is constrained inside the fragment container
UI does not become full screen
Reproduction Structure
NavigationPage
└── MainPage
└── PushModalAsync(
NavigationPage(
TabbedPage
)
)

TabbedPage
├── ContentPage1
├── ContentPage2
└── ContentPage3

Then:

await Navigation.PushAsync(new DetailPage());
Sample Code
await Navigation.PushModalAsync(
new NavigationPage(new BCAMainPage())
);

BCAMainPage:

public class BCAMainPage : TabbedPage
{
public BCAMainPage()
{
On<Microsoft.Maui.Controls.PlatformConfiguration.Android>()
.SetToolbarPlacement(ToolbarPlacement.Bottom);

    Children.Add(new Page1());
    Children.Add(new Page2());
}

}

Inside Page1:

await Navigation.PushAsync(new DetailPage());

Link to public reproduction project repository

No response

Version with bug

10.0.60

Is this a regression from previous behavior?

Yes, this used to work in .NET MAUI

Last version that worked well

10.0.50

Affected platforms

Android

Affected platform versions

.NET MAUI 10.0.60 Android only

Did you find any workaround?

No response

Relevant log output

Activity

  1. tranhoangnam16705 commented on May 7, 2026

    @tranhoangnam16705
    Author
    untitled.mp4
  2. tranhoangnam16705 commented on May 7, 2026

    @tranhoangnam16705
    Author
  3. NafeelaNazhir commented on May 7, 2026

    @NafeelaNazhir
    Contributor

    This issue has been validated in Visual Studio Code 1.119.0 with .NET MAUI versions 10.0.51 & 10.0.60. It can be reproducible on Android platform from version 10.0.60.

    10.0.60 10.0.51
    Screen.Recording.2026-05-07.at.1.45.45.PM.mov
    Screen.Recording.2026-05-07.at.1.44.11.PM.mov
  4. skha83 commented on May 7, 2026

    @skha83

    The reason for this regression is this PR #32878 which solved this problem CommunityToolkit/Maui#2708

    The old implementation blindly removed the TabBar in every situation, which caused problems when you opened a simple popup/dialog, so just reverting to the old implementation is not a solution. I don't know how these situations are handled on iOS. But there seems to be at least two different use cases:

    • The TabBar should not be removed when opening a dialog/popup.
    • The TabBar should maybe be removed if the page opening the new page is part of a navigation flow inside a NavigationPage.

    But what if you want to open a popup from the same page where you want to navigate to the sub page? how would it know when to remove or not remove the TabBar? if instead of calling await Navigation.PushAsync(new NewPage7()) you use await Navigation.PushModalAsync(new NewPage7()) the TabBar disappear, but then the back NavigationButton is not shown. Is it expected that the Tabbar disappear when opening a subpage, when a TabBar is shown at the bottom, or was this just a side effect of the old implementation?

    Maybe @jfversluis has some thoughts on this.

  5. added this to the .NET 10 SR7 milestone on May 7, 2026
  6. added a commit that references this issue on May 20, 2026
    2f20d7c
  7. added a commit that references this issue on Jun 2, 2026
    0d53bd7
  8. added a commit that references this issue on Jun 11, 2026
    421783f
  9. added a commit that references this issue on Jun 22, 2026
    ff96ea1
  10. added a commit that references this issue on Jun 25, 2026
    8407eef
  11. added a commit that references this issue on Jul 3, 2026
    5b9c9fc
  12. added a commit that references this issue on Jul 6, 2026
  13. locked and limited conversation to collaborators on Aug 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area-navigationNavigationPagei/regressionThis issue described a confirmed regression on a currently supported versionpartner/syncfusionIssues / PR's with Syncfusion collaborationplatform/androidregressed-in-10.0.60s/triagedIssue has been revieweds/verifiedVerified / Reproducible Issue ready for Engineering Triaget/bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions