Add Support for Maui Community Toolkit Popups

[faizkhan005]

Description

I am getting this error while trying to close Maui CommunityToolkit popups
{System.NullReferenceException: Object reference not set to an instance of an object. at Prism.Ioc.IContainerProviderExtensions.Resolve[INavigationService](IContainerProvider provider) in /_/src/Prism.Container.Abstractions/IContainerProviderExtensions.cs:line 16 at Prism.Navigation.Xaml.Navigation.GetNavigationService(Page page) in D:\a\Prism\Prism\src\Maui\Prism.Maui\Navigation\Xaml\Navigation.cs:line 122 at Prism.Navigation.PrismWindow.PrismWindow_ModalPopping(Object sender, ModalPoppingEventArgs e) in D:\a\Prism\Prism\src\Maui\Prism.Maui\Navigation\PrismWindow.cs:line 87

here is the link to sample project https://github.com/faizkhan005/PrismPopupIssues

Steps to Reproduce

1. Download the sample project and run
2. on main page press Sample Popup button (popup appears)
3. now try clicking outside the popup error message is thrown

Platform with bug

.NET MAUI

Affected platforms

iOS, Android

Did you find any workaround?

No response

Relevant log output

[dansiegel]

This is not directly a bug. Prism does not currently support the Community Toolkit. We will consider adding an extension point at some point but this isn't likely to get much priority unless we see real demand from the Prism Community.

[skha83]

I'm running into the same problem. The old version of popups from Community Toolkit worked without problems with Prism. But now after .NET 10 was released yesterday, I'm forced to update the Community Toolkit Nuget package, as the old version 11.2.0 has a constraint on .NET versions larger than 9, which make it necessary to update to version 12.3.0, if you want to run .NET 10.

This new version only support the new Popup version 2. I have pushed this upgrade of Popups V2 for several months, because I saw a lot of issues created on the topic at the Community Toolkit GitHub repository.

Originally I was using the Mopups Nuget package for popups, but lack of support and updates of critical bugs, made the switch to Community Toolkit popups necessary at that time. I hope I don't have to switch my popup implementation back to Mopups once again.

Every developer will see this problem if they use Community Toolkit popups and want to upgrade to .NET 10, while using Prism. With how .NET MAUI runs their service releases, you are forced to upgrade to .NET 10 if you want essential fixes for the newly released iOS 26 UI, which is currently a bit of a mess.