StateHasChanged () does not work in Blazor server app

[vsfeedback]

This issue has been moved from a ticket on Developer Community.

---

Is this a bug?
https://blog.unikktle.com/blazor-server-%e3%81%ae%e7%94%bb%e9%9d%a2%e3%81%a7%e5%87%a6%e7%90%86%e4%b8%ad%e3%82%aa%e3%83%bc%e3%83%90%e3%83%bc%e3%83%ac%e3%82%a4%e3%82%92%e8%a1%a8%e7%a4%ba%e3%81%99%e3%82%8b/

While implementing the Blazor Server screen with .Net Core 5.0, the desynchronization of the DB processing did not work well by linking the DB processing using EFCore and the Blazor screen, and I was addicted to not displaying the "in-process overlay".
-StateHasChanged () is not resolved even if the number of execution points is increased.
・ Even if the O / R mapper is changed to Dapper instead of EFCore, the problem persists.
-Execute await Task.Delay (1); and forcibly return the thread to the screen to solve the problem.

---

Original Comments

Feedback Bot on 9/26/2021, 01:07 AM:

We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.

---

Original Solutions

(no solutions)

[pranavkm]

Thank you for filing this issue. In order for us to investigate this issue, please provide a minimal project (ideally a GitHub repo) that illustrates the problem.

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.

See our Issue Management Policies for more information.