[Solution] MudBlazor not working with MAUI Blazor on iOS

[ScarletKuro]

If you are using .NET MAUI Blazor together with MudBlazor and target iOS you might run into a problem #6310
Currently, the AOT compiler runs into issue. This is a known problem dotnet/maui#14271

The only available workaround is to set these options:

<PropertyGroup>
   <MtouchLink>None</MtouchLink>
   <UseInterpreter>True</UseInterpreter> 
</PropertyGroup>

This will stay open and pinned until AOT gets improved or Microsoft makes these options as default dotnet/maui#13019

[theofanis]

Hey @ScarletKuro!

dotnet/maui#14271 is closed for quite some time now and I never had issues with MudBlazor on either iOS or MacCatalyst. Do you still consider this an issue and does the suggestion still apply?

For what is worth, I have tested with and without the interpreter and also use SdkOnly for linking and I don't have issues with MudBlazor during compilation.

Thanks!

[ScarletKuro]

Hi

Do you still consider this an issue and does the suggestion still apply?

Yes. There was report that FrozenSet is not working on iOS in Release builds, and we are affected too, because we use it in ParameterState on .NET8 in latest versions, and it requires interpreter to be enabled.
Or it would require to add the System.Collections.Immutable to exclusion:

<PropertyGroup>
	<MtouchInterpreter>-all,System.Collections.Immutable</MtouchInterpreter>
</PropertyGroup>

But for me it's easier to explain to the user to just enable the interpreter globally, rather than investigate every case.
To me the MAUI is still far from being ready for production.

[theofanis]

Cool thanks for verifying.

Yes. There was report that FrozenSet is not working on iOS in Release builds, and we are affected too, because we use it in ParameterState on .NET8 in latest versions, and it requires interpreter to be enabled. Or it would require to add the System.Collections.Immutable to exclusion:

<PropertyGroup>
	<MtouchInterpreter>-all,System.Collections.Immutable</MtouchInterpreter>
</PropertyGroup>

I am aware of this issue, got hit by it yesterday and it took me a few hours to find it. Sounds like you're talking about the same thing. There was an issue logged in the maui board as well, but it was closed a few days ago in favor of the CommunityToolkit one.

Actually, I already use the exclusion you shared to at least try to safeguard some of performance since my app is doing several encoding/hashing actions and still see MudBlazor working OK for what I do, so I thought to ask here.

But for me it's easier to explain to the user to just enable the interpreter globally, rather than investigate every case. To me the MAUI is still far from being ready for production.

I will be monitoring the issue in any case, thank you for the prompt reply!

[ivanpovazan]

The problem with FrozenSet seems to be fixed in .NET9 and the workaround for enabling the interpreter is not needed anymore. Could you try the latest .NET9 preview release to verify if it fixed the problem for you?

[ivanpovazan]

I have opened dotnet/runtime#101427 for tracking.