Ensure that _modalNavigationManager is always non-null when invoked in HandleOnBackPressed. If there's any possibility for a null value, consider adding appropriate fallback handling or logging to maintain robust modal navigation behavior.

just because this CallBack is a Java.Lang.Object, can we store the ModalNavigationManager as a WeakReference?

Good point! Done

Maybe this test should be only for Android?

Yea probably, thanks!

@kubaflo this one is a little interesting because the original author is returning false but they are opting out of all of our navigation logic

The fix here also feels incorrect because we are only running this test on android.

My first thought with how this would work is that if the user is overriding OnBackButotnPResed on page and they don't call the base class and then they return false

That by default we don't do anything at that point.

If they are opting out of calling our base class and returning false we can't really assume what to do for them at this point.

@pictos do you remember why we opted to call the OnBackPresed from the Dispatcher here?

The Dispatcher is from AndroidX, just for reference. I think this was implemented to enable modal pages to listen for and handle back button presses. We register the ComponentDialog here, and when the callback is triggered, we forward that event into Maui's structure.

yea, but this is what causes the infinite loop

Like, if I'm following the code right I feel like the fix here should just be deleting this code

						{
							customComponentDialog.OnBackPressedDispatcher.OnBackPressed();
						}

this just causes HandleBackPressed to get called infinitely when you return false

@kubaflo I think the fix here is to just delete this code completely

if (!preventBackPropagation && _modalNavigationManager.TryGetTarget(out var mnm))
						{
							customComponentDialog.OnBackPressedDispatcher.OnBackPressed();
						}

This whole situation is a bit of a mess :-/

I don't think the "OnBackButtonPressed" was fully thought through with Modal or Android really as we moved to MAUI

like, currently with a navigation page if you return false it'll cause a double back navigation and exit the app.

Technically from the API description I think the way you'd use this API would be more like this

		protected override bool OnBackButtonPressed()
		{
			if (mycustomLogic)
			{
				return true;
			}
			else
			{
				return base.OnBackButtonPressed();
			}
		}

I also worry about this change because if users call "base.OnBackButtonPressed" I think that's going to cause a double navigation back since the base class will also navigate back