Closed iserofeev closed 3 months ago
Thanks for the report, fixed in the next version!
Hello, I've just updated to the latest version, but I'm still seeing this problem. I hope it will be fixed in future releases, and I'd appreciate knowing in which version it will be addressed.
I couldn't replicate it with the latest version. It was included in v3.0.3, released on 09-09.
Hello,
After updating to version 2, we faced a SignalR problem when using only WebSockets as transport.
We successfully fixed it by editing the source code of HubConnection.cs.
The core of the problem is a null reference of NegotiationResult. It is called after the connection, but it is set only if SkipNegotiation is false (which is the default).
Setting NegotiationResult fixes this problem. I hope you will address this in your source code in future updates.
Thanks for a great asset!