Build in AuthenticationStateProvider breaks after trimming

[iits-timon-holzhaeuser]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

Just tried the new API from #52769 and replaced my implementation with it.
After the trimming during dotnet publish I get an exception as soon as the app tries to hand over to WebAssembly:

May relate to #52947 as I noticed that the AuthenticationStateData is using a IList<KeyValuePair<string, string>> but that is only my wild guess.

I'm not using the JSON Source Code Generation Serialization

After removing this line on client:

builder.Services.AddAuthenticationStateDeserialization();

And this line on the server side:

.AddAuthenticationStateSerialization(options => options.SerializeAllClaims = true)

The app worked again as expected.

Expected Behavior

The handover to Web Assembly should work flawless.

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version

9.0.0-preview.5.24306.7

Anything else?

No response

[mguinness]

Also try adding the following to PropertyGroup section in the csproj file.

<_ExtraTrimmerArgs>--keep-metadata parametername</_ExtraTrimmerArgs>

[iits-timon-holzhaeuser]

This fixed the issue, thanks 🎉 Added the Property to the client project, and now it works as expected.

So, most likely this will be fixed by PR dotnet/runtime#102850? Or is this the PR which made the _ExtraTrimmerArgs possible?

[mguinness]

The PR should obliviate the need for _ExtraTrimmerArgs , maybe @sbomer can clarify further.

[sbomer]

Yes, with that PR you should not need --keep-metadata parametername.

I'm not familiar with the scenario though - if this is using JSON serializer without the source generator, you might hit other trimming-related problems. Any warnings you get with SuppressTrimAnalysisWarnings=true are indicative of potential problems.

I'll close this issue because I believe the specific failure is fixed by dotnet/runtime#102850, but feel free to reopen if that's not the case.

[halter73]

I'm reopening because while there are workarounds, we want to make sure nothing is over-trimmed in the default configuration.