"The current thread is not associated with the Dispatcher" with OnInitializedAsync()

[samcarswell]

I have the following the test code:

var filtTab = RenderComponent<FilterTable<BatchVMDTO>>(
    parameters => parameters
        .Add(p => p.GetFunc, GetData)
    );

await filtTab.InvokeAsync(() =>
    {
        filtTab.WaitForAssertion(
            () =>
                Assert.Equal(
                    "Displaying 1 to 100 of 1000 / 1000",
                    filtTab.Find("#pager-count").InnerHtml
                    )
            );
    }
);

The FilterTable component runs OnInitializedAsync which calls and awaits several async functions. I am aiming to wait for the component to be initialised and then assert the value of some element. However I get the following error when await Task.Run(StateHasChanged); is called in OnInitializedAsync() of FilterTable:

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.

[egil]

Have you tried the following?:

var filtTab = RenderComponent<FilterTable<BatchVMDTO>>(
    parameters => parameters
        .Add(p => p.GetFunc, GetData)
    );

filtTab.WaitForAssertion(
            () =>
                Assert.Equal(
                    "Displaying 1 to 100 of 1000 / 1000",
                    filtTab.Find("#pager-count").InnerHtml
                    )
            );

[samcarswell]

Sorry I should have included this with the post: that was what I originally tried, but unfortunately the same result.

[egil]

... However I get the following error when await Task.Run(StateHasChanged); is called in OnInitializedAsync() of FilterTable:

If I understand correctly what you are writing, then you need to wrap your call to StateHasChanged into an InvokeAsync call in your component. E.g.:

Task.Run(InvokeAsync(StateHasChanged));`

However, if you have the code you list above, then you are likely doing something unusual in Blazor. I cannot think of a reason why you would call StateHasChanged from a new task you manually create with Task.Run.