Going back using 'Shell.Current.GoToAsync("..")' causes a crash, but only when using a Mouse on an Android.

[Realinspirer]

Description

...and due to a completely out of the world reason. At least that's what I am assuming.

So, I have a secondary back button in the ContentPage, which calls GoToAsync("..") to go back. Please note that I was using Windows Subsystem for Android™️ for this testing, but I do believe this might be reproducible on any Android device with a connected mouse (though not tested).
The button works perfectly when I tap it with my finger, but when I use the cursor to click the button, it crashes, and throws a NullReferenceException. I think what actually happens is MAUI tries to send a onhover call after the back button is clicked, but the reference is cleared, and it crashes as a result, whereas in a tap, it doesn't have to send that hover event.

Here's a video demonstration:

43gg.mp4

Or I might be completely wrong about this, because it seems that abnormal.

Steps to Reproduce

1. Add two pages to a new app, and navigate to second page from first page.
2. Add a button to the second page, and have it call Shell.Current.GoToAsync("..")
3. On WSA/Android with a mouse, click on the Back button to get the NullReferenceException.

Link to public reproduction project repository

https://github.com/Realinspirer/tempcheck

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 13 (others not checked)

Did you find any workaround?

A cheap workaround, kind of obvious, but may not work at times, is - disabling the back button before the page transition, so that the after events doesn't get into account.

Relevant log output

**System.NullReferenceException:** 'Object reference not set to an instance of an object.'

[Realinspirer]

Checked on a physical android device with a mouse, and it crashes the same. Is there a way to avoid this?

Hi @Realinspirer. We have added the "s/needs-repro" label to this issue, which indicates that we require steps and sample code to reproduce the issue before we can take further action. Please try to create a minimal sample project/solution or code samples which reproduce the issue, ideally as a GitHub repo that we can clone. See more details about creating repros here: https://github.com/dotnet/maui/blob/main/.github/repro.md

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.

[PureWeen]

Do you have a full stack trace as well?

[Realinspirer]

I added a public repository for the people. Also, I am unable to fetch the exception stack trace, maybe because it's caused internally, or I don't know.

[PureWeen]

@Realinspirer if you grab a logcat after the crash that should have it

https://learn.microsoft.com/en-us/xamarin/android/deploy-test/debugging/android-debug-log?tabs=windows

Hi @Realinspirer. 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.