Popup V2, Background turns black with Popup v2 in version 12.1.0 (not in 12.0.0)

[ufermanninfotech]

Hi everyone,

I’ve encountered an issue when switching between CommunityToolkit.Maui NuGet versions 12.0.0 and 12.1.0.

In my project, I’m using the new Popup v2. When I update to version 12.1.0, the entire background behind the popup turns black. This does not happen in version 12.0.0. The issue appears only when switching the NuGet version — there are no other changes to styles, theme handling, or any related configuration.

To further investigate, I tried to reproduce the issue in a small sample project, but there the problem does not occur.

Has there been any change in how popups handle background rendering between these two versions? Or is this a known issue?

Thanks in advance for your help!

[bijington]

We now place a BoxView behind the popup to handle touch interaction. Do you have any default styling set for a BoxView that could cause this?

[ufermanninfotech]

Thanks for the quick response!

You were absolutely right — I had the following global style defined in my Styles.xaml:

<Style TargetType="BoxView">
    <Setter Property="Color" Value="{AppThemeBinding Light={StaticResource Gray950}, Dark={StaticResource Gray200}}" />
</Style>

After commenting out this style, the black background issue with the popup is gone. So that seems to have been the cause — thank you!

Interestingly, this exact style also exists in my minimal test project (as it’s part of the default template), but there it doesn’t seem to have any visual impact on the popup background. I’m not sure why the behavior differs between the two projects — perhaps due to some other interaction or layout detail that I’m missing. Someone any Idea?

In any case, I now have a working solution. Thanks again for the helpful pointer!

[cat0363]

@bijington
I was having the same issue. Is the solution you provided just a temporary workaround? Will we be able to get around this in a future release without having to comment out the BoxView style?

[bijington]

@cat0363 yes the this workaround can be removed in the next release

[cat0363]

@bijington , Thank you for your quick reply. I'm looking forward to the next release.