[Android] Shell BackButtonBehavior binding Command to valid ICommand causes back button to disappear

[rjygraham]

Description

Binding to a valid ICommand on Shell.BackButtonBehavior causes back button to disappear on Android (maybe iOS as well, no idea on Windows since it is not currently supported).

Steps to Reproduce

1. File -> New .NET MAUI App
2. Create multi-page Shell App
3. On SecondPage create BackButtonBehavior and bind Command to a valid ICommand on the BindingContext:

 <Shell.BackButtonBehavior>
      <BackButtonBehavior
          Command="{Binding BackCommand}"
          IsEnabled="True"
          IsVisible="True">
          <BackButtonBehavior.IconOverride>
              <FontImageSource FontFamily="OpenSansSemibold" Glyph="&#x2039;" />
          </BackButtonBehavior.IconOverride>
      </BackButtonBehavior>
  </Shell.BackButtonBehavior>

4. Run the app and navigate to SecondPage
5. Observe back button is not visible
6. While app is still running, use Hot Reload to change the BackButtonBehavior Command binding to invalid ICommand and observe the back button appears but does nothing since binding is invalid

RC3 reproduction repo can be found here:
https://github.com/rjygraham/MauiShellNav

Reproduction video can be found here:
https://raw.githubusercontent.com/rjygraham/MauiShellNav/main/videos/BackButtonBehavior.mp4

Version with bug

Release Candidate 3 (current)

Last version that worked well

Unknown/Other

Affected platforms

Android, I was not able test on other platforms

Affected platform versions

Android 11

Did you find any workaround?

None yet

Relevant log output

No response

[v-longmin]

Verified repro on Android 12.0 with VS 17.3.0 Preview 1.0 [32427.505.main]. Repro project:
MauiShellNav-main.zip

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.

[espenrl]

The same happens on .NET 7 SR 1.

[mikkpaasuke]

Still an issue. This leaves some particular navigation requirements for a client of mine dead in the water.