FlyoutPage inside a NavigationPage causes different behavior between Android and iOS #18228
Labels
area-controls-flyoutpage
FlyoutPage
area-navigation
NavigationPage
migration-compatibility
Xamarin.Forms to .NET MAUI Migration, Upgrade Assistant, Try-Convert
platform/android 🤖
s/triaged
Issue has been reviewed
s/verified
Verified / Reproducible Issue ready for Engineering Triage
t/bug
Something isn't working
Milestone
Description
We are migrating our app from Xamarin forms (5.0.0.2612) to Maui in the last weeks and we encountered a deal breaker when testing the android version. We use a single navigationPage for all the app lifeCycle, so when the user first opens the app, the root page is a LoginPage, if authentication succeed, he is directed to a logged area, that is a FlyoutPage with all the app features.
After migrating the project to Maui (.net 7 - 7.0.96), we tested on iOS and this behavior worked just fine (beside some events that the navigationPage is trigging in a different order), but on Android the Hamburger menu did not appear. After testing the flyoutSample we discover that the problem was because the FlyoutPage is not the application MainPage.
The expected behaviour would be two toolbars appearing, on Xamarin Forms (Android and iOS) and Maui iOS we use the
NavigationPage.HasNavigationBar="False"
to hide one of then, but this don't seems to work either on Maui Android.Here same examples:
Maui iOS
Maui iOS with NavigationPage.HasNavigationBar="False" in the FlyoutPage:
Maui Android in both cases:
My guess that this is a problem caused by the new Navigation on Android, since on iOS its stiils uses the old one from XF.
Steps to Reproduce
No response
Link to public reproduction project repository
https://github.com/DouglasGiovanella/MauiFlyoutSample
Version with bug
7.0.96
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
No response
Did you find any workaround?
Just changing the application MainPage to use directly the FlyoutPage, for us is a big structural change, but maybe can help someone else.
Relevant log output
No response
The text was updated successfully, but these errors were encountered: