You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Android TabbedPage inside Modal Navigation does not overlay BottomNavigationView after PushAsync in .NET MAUI 10.0.60 #35331
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
)
)
public class BCAMainPage : TabbedPage
{
public BCAMainPage()
{
On<Microsoft.Maui.Controls.PlatformConfiguration.Android>()
.SetToolbarPlacement(ToolbarPlacement.Bottom);
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.
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?
Activity
tranhoangnam16705 commentedon May 7, 2026
untitled.mp4
tranhoangnam16705 commentedon May 7, 2026
MauiTabPageTest.zip
NafeelaNazhir commentedon May 7, 2026
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.
Screen.Recording.2026-05-07.at.1.45.45.PM.mov
Screen.Recording.2026-05-07.at.1.44.11.PM.mov
skha83 commentedon May 7, 2026
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:
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.
[Android] Fix BottomNavigationView remaining visible for TabbedPage …
[Android] Fix BottomNavigationView remaining visible for TabbedPage …
[Android] Fix BottomNavigationView remaining visible for TabbedPage …
[Android] Fix BottomNavigationView remaining visible for TabbedPage …
[Android] Fix BottomNavigationView remaining visible for TabbedPage …
[Android] Fix BottomNavigationView remaining visible for TabbedPage …
June 8th, Candidate (#35716)