Flyout button is visible for a split second when navigating back to home page in Android

[cabauman]

Description

Flyout button is visible for a split second when navigating back to home page in Android when Flyout is disabled with Shell.FlyoutBehavior="Disabled". When Microsoft.Maui.Controls version is 8.0.21 it shows the flyout button for a split second. But when Microsoft.Maui.Controls version is 8.0.7 it shows the back button for a split second. This happens with both emulator and device.

I tried iOS (device and emulator), and it smoothly transitions.

maui8.0.7-android-nav.webm
maui8.0.21-android-nav.webm

Steps to Reproduce

1. Create a new Maui app
2. Create a new page and register the route
3. Add a button to the main page to navigate to it , e.g. Shell.Current.GoToAsync("page2")
4. Start the app and navigate to the other page
5. Press the back button (either device or ui)

Expected Behavior
nav bar should smoothly transition to the home page version (title with no icon)

Actual Behavior
appears glitchy: flyout button appears for a split second before disappearing, and title jumps to fill the empty space

Link to public reproduction project repository

https://github.com/cabauman/MauiAndroidNavBug

Version with bug

8.0.21 SR4.1

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 11 and up

Did you find any workaround?

Haven't found a workaround so far. I tried NavigationPage navigation instead of Shell but same result.

Relevant log output

No response

[PureWeen]

@cabauman does this one look like a duplicate of #18867?

[cabauman]

Hi @PureWeen 👋
Ah yes, same issue, except now it's the flyout/hamburger icon instead of the arrow. I searched the GitHub issues quite a while for a similar issue before creating this one, but failed to find anything because of our choice of keywords.

[PureWeen]

I'm going to close this one as a duplicate for now.

We have this one linked so we can validate this scenario is also fixed!