-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FlyoutPage's menu icon not showing, when used in a NavigationPage on Android #22116
Comments
Verified this issue with Visual Studio 17.10.0 Preview 5 (8.0.14& 8.0.21).I can repro this issue |
/similarissues |
Hi I'm an AI powered bot that finds similar issues based off the issue title. Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you! Open similar issues:
Closed similar issues:
|
Hi, exactly the same happens to me, is there any way to resolve this? |
The label triaged, it means it is out of backlog? This issue is for me the only bug i need to fixed to get my production app out. |
Burger still not appearing randomly in MAUI 8.0.80. |
Description
In my apps i load the flyoutpage (Master/Detail) in a Navigationpage. Then i can load other pages, like a Pin Auth page on top of my menu/app so users don't lose their position in the apps when switching apps and must provide Pin etc
This works great on Xamarin and also on iOS MAUI. But on Android the icon/hamburger image is not showing so i can't use the menu through the icon.
Working:
Not working on Android (Just Works on IOS)
Steps to Reproduce
No response
Link to public reproduction project repository
https://github.com/mnidhk/MAUI/tree/main/FlyoutPageSample
Version with bug
8.0.21 SR4.1
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?
No, no workaround found
Relevant log output
No response
The text was updated successfully, but these errors were encountered: