SignalR uncaught exception in Blazor Webassembly using automatic reconnect

[lamcyborg]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

Using Microsoft.AspNetCore.SignalR.Client in a client hosted Blazor Webassembly, using the following connection:

Using the following retry-policy:

When disconnecting the network between the client and the server multiple times, SignalR throws an exception and the client needs to be restarted.

The console log produce the following log messages:

The Closed, Reconnecting, and Reconnected events are connected mainly for logging and the StartAsync() method on the connection is try-catced but we never end up in the catch section. The exception seem to be thrown in an uncatchable context.

Expected Behavior

The expected behavior would be that the connection tries to reconnect without exception.

Steps To Reproduce

No response

Exceptions (if any)

System.InvalidOperationException

.NET Version

8.0.13

Anything else?

No response

[BrennanConroy]

The exception seem to be thrown in an uncatchable context.

What is the hidden stack frame? That seems to be your code where you should be catching the exception if you don't want it to be unhandled.

[lamcyborg]

The hidden stack frame is there because the code comes from an unreleased product.

The try-catch is there but it never ends up in the catch.

[BrennanConroy]

You don't have a try catch around the InvokeAsync call.

if (this.connection.State == HubConnectionState.Connected)
{
    try
    {
        await this.connection.InvokeAsync("UpdateAccessToken", token).ConfigureAwait(false);
    }
    catch { }
}

[dotnet-policy-service]

This issue has been resolved and has not had any activity for 1 day. It will be closed for housekeeping purposes.

See our Issue Management Policies for more information.

[lamcyborg]

Thanks @BrennanConroy. A huge mistake on our side. Adding a handler as suggested resolved our problem.