Skip to content

[Blazor] State management - StateHasChanged+InvokeAsync #34237

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
guardrex merged 3 commits into from
Dec 12, 2024
Merged

[Blazor] State management - StateHasChanged+InvokeAsync #34237

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
8631144
[Blazor] State management - StateHasChanged+InvokeAsync
hakenr Nov 28, 2024
8d24a7d
Update aspnetcore/blazor/state-management.md
guardrex Dec 1, 2024
e53ac22
Update aspnetcore/blazor/state-management.md
guardrex Dec 12, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion aspnetcore/blazor/state-management.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -791,7 +791,7 @@ When implementing custom state storage, a useful approach is to adopt [cascading

## Troubleshoot

In a custom state management service, a callback invoked outside of Blazor's synchronization context must wrap the logic of the callback in <xref:Microsoft.AspNetCore.Components.ComponentBase.InvokeAsync%2A?displayProperty=nameWithType> to move it onto the renderer's synchronization context.
When using a custom state management service, if you want to support state modifications from outside Blazor's synchronization context (for example from a timer or a background service), all consuming components must wrap the `StateHasChanged` call in <xref:Microsoft.AspNetCore.Components.ComponentBase.InvokeAsync%2A?displayProperty=nameWithType>. This ensures the change notification is handled on the renderer's synchronization context.

When the state management service doesn't call <xref:Microsoft.AspNetCore.Components.ComponentBase.StateHasChanged%2A> on Blazor's synchronization context, the following error is thrown:

Expand Down