Reconnecting Issue in Blazor Server

Question

Hi,

We have set up our Blazor server application(.NET7) and hosted it. Often we are getting the below error description and we have to reload the page to make it work. frequently we are getting this issue when we are having worked on the browser tab of a blazor page and if we want to go to another tab for some other work and after comeback to the blazor page, We have been referring to some articles related to the above and we expected after .NET7 new release we can get it sorted out. However, the issue is still there and we are not able to fix the issue yet.

is it a SignalR connection issue or anything else, can anyone help me regarding this ??

Answer 1

Chrome is very aggressive about shutting down websockets in tabs that are not currently displayed. After a disconnect, the signal/r hub has a limited lifetime (20 seconds I believe) where reconnects are allowed. Once the signal/r times out the connection, the client app has no way to reconnect. See:

https://learn.microsoft.com/en-us/aspnet/signalr/overview/guide-to-the-api/handling-connection-lifetime-events

This is just a disadvantage of the blazor server design.