Wrong behaviour configuring stateful reconnect

[bdovaz]

https://learn.microsoft.com/en-us/aspnet/core/signalr/configuration?view=aspnetcore-8.0&tabs=dotnet#configure-stateful-reconnect

@davidfowl I have the same problem as @quytrieu37 in #54818 and I see he did not manage to solve it....

I mean, between reconnections I get different connection ids.... The client is configured with WithAutomaticReconnect and WithStatefulReconnect. In the documentation it doesn't say anything about not setting WithAutomaticReconnect and I have removed it but when I do that what happens is that the HubConnection goes directly to the disconnected state...

Is there any way to debug this problem to know if it is a problem in the client or in the server? Even if I set the logs in client and server to Trace I don't see anything useful beyond the negotiation url that adds the withstatefulreconnect=true (or something similar).

Thanks.

[davidfowl]

cc @BrennanConroy

[co-dax]

See #54818 (comment) for a possible workaround.

[Mise22]

I have the same issue. I can confirm WithAutomaticReconnect is needed. In the source code I can't find where the ConnectionId preservation is supposed to happen.
(full reply #54818 (reply in thread))