Issue with NavigationPage Root Navigation in .NET MAUI - ANDROID

[DanielCauser]

Description

Hi Team,

In Xamarin Forms, I used a NavigationPage as my App.MainPage, and handled navigation via NavigationPage.Navigation. This approach worked well with the tools available in Xamarin Forms, particularly for navigation flows where the root page of the app changes—such as switching from a LoginPage (a full-screen page) to a FlyoutPage or even a TabbedPage as the new root page.

As we know, the NavigationPage in Xamarin Forms did not allow direct changes to the root page. To work around this, I used the following pattern:

NavigationPage.Navigation.InsertPageBefore(new FlyoutPage(), NavigationPage.Navigation.NavigationStack[0]);
NavigationPage.Navigation.PopToRootAsync(false);

This approach involves inserting the new root page (FlyoutPage) before the current root page in the navigation stack and then popping to root. This pattern worked effectively and is also used by libraries like Sextant from ReactiveMarbles.

Steps to Reproduce

1. Create a brand new app
2. On App.cs set the MainPage = new NavigationPage(new ContentPage());
3. On your ContentPage, create a button that navigates you to a FlyoutPage
4. The code that navigates to the Flyout should be like this

Expected Outcome

The expected outcome is that the Page on Android should look like this:

The Actual outcome

The FlyoutPage is not identified as Flyout, there is no Hamburguer button.

Link to public reproduction project repository

https://github.com/DanielCauser/SextantNavigation/tree/daca/maui_pure_as_sextant/SextantNavigation

Version with bug

8.0.40 SR5

Is this a regression from previous behavior?

Yes, this used to work in Xamarin.Forms

Last version that worked well

Unknown/Other

Affected platforms

Android

Affected platform versions

Android 13 and Above

Did you find any workaround?

There is known workaround that would still allow us to user NavigationPage as the main navigation source for the app.

The only way to make it work is to Change the App.MainPage, which breaks all the principles applied in enterprise projects.

Relevant log output

No response

[similar-issues-ai]

We've found some similar issues:

• FlyoutPage inside a NavigationPage causes different behavior between Android and iOS #18228 , similarity score: 86%
• Android FlyoutPage problems when FlyoutPage::Flyout is a NavigationPage. #14561 , similarity score: 83%
• NavigationPage shows title bar before navigating #21134 , similarity score: 82%
• Android FlyoutPage does not display navigation bar NET 8 #19623 , similarity score: 81%

If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.

Note: You can give me feedback by 👍 or 👎 this comment.

[ninachen03]

This issue has been verified using Visual Studio 17.12.0 Preview 2.1(8.0.91 & 8.0.21). Can repro this issue at Android platform.

[Shalini-Ashokan]

This issue has been verified in Visual Studio Code 1.104.1 with MAUI version 9.0.110 It can be reproduced on the Android platform.

25187-Android.mov

[KarthikRajaKalaimani]

Hi @DanielCauser ,

According to the official .NET MAUI documentation, a FlyoutPage is intended to be used only as the root page of the application. It is not supported to embed a FlyoutPage within other page types such as NavigationPage.

Documentation link : https://learn.microsoft.com/en-us/dotnet/maui/user-interface/pages/flyoutpage?view=net-maui-9.0

To resolve this issue, set the FlyoutPage as the application's root page directly, rather than navigating to it from another page like NavigationPage.

Application.Current!.Windows[0].Page = new MainPage();
App.NavigationManager.Navigation.PopToRootAsync(false);

Screen.Recording.2025-09-25.at.5.59.57.PM.mov