Custom FlyoutIcon visible although FlyoutBehavior set to disabled on Android an IOS

[FM1973]

Description

When I add a custom FlyoutIcon to shell, the icon is visible on a page although I´ve set Shell.FlyoutBehavior="Disabled" on the page and inside shellContent.
This happens on Android (v12 in my case) and iOS (15 in my case).
When you toch the icon on iOS, nothing happens...
When you do the same an Andoid an error occurs (No drawer view found with gravity LEFT).

When I remove the custom icon, all works as expected (hamburger menu not being displayed).

Steps to Reproduce

1. Create a new maui app
2. Create a shell with some shell contents
3. For one shell content set Shell.FlyoutBehavior="Disabled"
4. Set this shell content as the first item (start page)
5. Add a custom FlyoutIcon (FlyoutIcon="flyout_icon.png")
6. Start the app and the icon is being displayed although it shouldn´t
7. Stop the app and remove the custom icon
8. Start the app and the hamburger menu icon is not being displayed as it sould

Expected: The custom flyout icon should not be displayed on pages with Shell.FlyoutBehavior="Disabled"
Actual outcome: The custom flyout is being displayed on pages with Shell.FlyoutBehavior="Disabled"

Version with bug

6.0.400

Last version that worked well

Unknown/Other

Affected platforms

iOS, Android

Affected platform versions

iOS 15, Android 12

Did you find any workaround?

No response

Relevant log output

No response

[FM1973]

One more thing I noticed now: a custom flyouticon replaces even the backbutton. Don´t think this is intended.

[ghost]

We've moved this issue to the Future milestone. This means that it is not going to be worked on for the coming release. We will reassess the issue following the current release and consider this item at that time.

[Zhanglirong-Winnie]

Verified this issue with Visual Studio Enterprise 17.8.0 Preview 1.0. Can repro on iOS and android platform.

[kubaflo]

@jfversluis @Zhanglirong-Winnie @FM1973 I could also replicate this bug on both Android and iOS. Here's the PR of the fix that I propose: #20087