-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Using FlyoutPage with NavigationPage not working on dotnet 8 #19243
Comments
I'm suffering from the same issue. The complete navigationbar seems unchanged |
This is a duplicate issue - not sure what the number was. There's already a fix awaiting GA. The issue is/was with NavigationPage titles, not Flyout menu. |
Here it is #18902 (comment) |
We think this was fixed in the upcoming SR1 (#18684), and you can verify this by using the nightly builds: https://github.com/dotnet/maui/wiki/Nightly-Builds Please try it out and let us know. |
Hi @filipemelo. We have added the "s/needs-info" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time. |
Duplicate of #18050 |
Thank you for the answers. I will close as this is duplicated. |
Description
Using combo with FlyoutPage and NavigationPage is not changing the title.
Steps to Reproduce
This is happening on dotnet 8.0.0.3
Link to public reproduction project repository
https://github.com/filipemelo/MauiStudy/tree/master/AppFlyoutPage
Version with bug
8.0.3
Is this a regression from previous behavior?
Not sure, did not test other versions
Last version that worked well
Unknown/Other
Affected platforms
Android
Affected platform versions
Android S22
Did you find any workaround?
I tried several, but I was able to do it.
The only thing that changed the tile was using a Navigation.PushAsync(), but I don't want this behavior, because I want to change to point to a new NavigationPage with a new Page inside.
Relevant log output
No response
The text was updated successfully, but these errors were encountered: