1. Feedback
  2. Blazor
  3. 13671

Welcome to the Blazor feedback portal. We’re happy you’re here! If you have feedback on how to improve the Blazor, we’d love to hear it!

  • Check out the features or bugs others have reported and vote on your favorites. Feedback will be prioritized based on popularity.
  • If you have feedback that’s not listed yet, submit your own.

Thanks for joining our community and helping improve Syncfusion products!

1
Vote

SfToast Show() calls StateHasChanged() syncronously

The following error is thrown when calling the Show() method on a SfToast component instance from an async method on an async thread. Basically, any time any Blazor code calls StateHasChanged() in an async method, it should instead be called using InvokeAsync(StateHasChanged), regardless of what component it is in. I would assume there are other places this type of issue may occur. This bug makes the SfToast component unusable for me at the moment.


Error: System.InvalidOperationException: The current thread is not associated with the Dispatcher. Use InvokeAsync() to switch execution to the Dispatcher when triggering rendering or component state.
   at Microsoft.AspNetCore.Components.Dispatcher.AssertAccess()
   at Microsoft.AspNetCore.Components.RenderTree.Renderer.AddToRenderQueue(Int32 componentId, RenderFragment renderFragment)
   at Microsoft.AspNetCore.Components.ComponentBase.StateHasChanged()
   at Syncfusion.Blazor.Notifications.SfToast.Show(ToastModel toastObj)