Open kirankumar4vr opened 1 year ago
We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.
Verified this issue with Visual Studio Enterprise 17.7.0 Preview 1.0. Can repro on iOS platform with sample project. FlyoutPages
On iOS Right now based on your example it looks like this is working as intended. If you hide the back button on Navigation Page with a flyout we have logic to handle if it should show the flyout button or the back button. In your example it is showing a flyout button and the custom button you added to the navigation title.
If you are interested in implementing custom logic for displaying the default toolbar buttons I suggest overriding ShouldShowToolbarButton() as part of the FlyoutPage and implement your logic from there.
We've added this issue to our backlog, and we will work to address it as time and resources allow. If you have any additional information or questions about this issue, please leave a comment. For additional info about issue management, please read our Triage Process.
Description
In a flyout pages app, when the back button is set to false for a navigation page using the below line
NavigationPage.SetHasBackButton(this, false);
page is showing the flyout menu icon on iOS. if the above line is not set, page top bar simply shows a back button as expected. However, on Android, it is working as expected. Android screenshot https://raw.githubusercontent.com/kirankumar4vr/FlyoutPages/main/Images/Android.pngiOS screenshot https://raw.githubusercontent.com/kirankumar4vr/FlyoutPages/main/Images/iOS.png
Steps to Reproduce
Link to public reproduction project repository
https://github.com/kirankumar4vr/FlyoutPages
Version with bug
7.0 Release Candidate 1
Last version that worked well
Unknown/Other
Affected platforms
iOS
Affected platform versions
iOS 14+
Did you find any workaround?
NA
Relevant log output
No response