[Blazor WebApp] RenderMode InteractiveAuto and Could not reconnect to the server message

[mohaaron]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

I am using the new Blazor WebApp template using render mode InteractiveAuto globally and am getting the SignalR reconnect message even when I'm showing that the components are running in WASM. Was I wrong to think that once the render mode changed from Server to WASM that the server reconnect would not happen anymore? I was hoping that using the new WebApp template would help with the server reconnection issues.

There is some discussion here regarding how to test for the current render mode. Is the code below not a good test?

protected override void OnInitialized()
{
    if (OperatingSystem.IsBrowser())
    {
        currentRenderMode = "WASM";
    }
    else
    {
        currentRenderMode = "Server";
    }
}

Expected Behavior

Once the render mode has automatically changed to WASM there would no longer be reconnection required due to the SignalR connection not being needed.

Steps To Reproduce

Let a running WebApp sit idle until the reconnection message appears.

Exceptions (if any)

No response

.NET Version

8.0.100

Anything else?

No response

[mohaaron]

I wonder, does this have something to do with the OIDC authentication that's happening on the server side of the app and is somehow keeping a SignalR connection open?

[ghost]

Thank you for filing this issue. In order for us to investigate this issue, please provide a minimal repro project that illustrates the problem without unnecessary code. Please share with us in a public GitHub repo because we cannot open ZIP attachments, and don't include any confidential content.

[mohaaron]

I have the Github repo here that I've been using to understand how authorization works in the new WebApp template, but it's not having the same SignalR reconnect issue as my other project which I have pictured here. The project having this problem is not something I can share. Does anyone have some idea why the WebApp template would have this issue? It feels to me like maybe the authorization or something is hanging on to the SignalR connection and it's preventing 100% of the functionality from moving over to using the WASM components.

[MackinnonBuck]

Thanks for reaching out. We have some auto mode improvements coming in .NET 8.0.200, but until then, could you please try the applying the fix manually as described in this comment and see if it resolves your issue?

[mohaaron]

Thanks for reaching out. We have some auto mode improvements coming in .NET 8.0.200, but until then, could you please try the applying the fix manually as described in this comment and see if it resolves your issue?

Hi Buck, I appreciate your response. I will check into what you have suggested and response here with the results.

Thank you

[dotnet-policy-service]

Hi @mohaaron. We have added the "Needs: Author Feedback" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

[dotnet-policy-service]

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.