Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix antiforgery token trimming in Blazor WebAssembly prerendering
Add DynamicDependency attributes to prevent IL trimming of antiforgery type.
Description
When a Blazor WebAssembly app with Individual Identity authentication is published with
PublishTrimmed=true, the antiforgery token persisted during SSR is not restored during the SSR-to-WASM handoff. This causes the<AntiforgeryToken>component to render nothing in interactive mode, breaking form submissions.Root cause: The IL trimmer removes
DefaultAntiforgeryStateProvider.CurrentTokenproperty andAntiforgeryRequestTokenconstructor because they're only accessed via reflection by the persistent state system.Fix: Add
[DynamicDependency(JsonSerialized, typeof(...))]attributes onWebAssemblyHostBuilder.InitializeDefaultServices()to preserve:DefaultAntiforgeryStateProvider- ensures the[PersistentState] CurrentTokenproperty is preservedAntiforgeryRequestToken- ensures the constructor and properties are preserved for JSON deserializationKnown workarounds:
Fixes #64693