When using Server Sent Events transport there are at least 2 issues caused by underlying implementation of sse_channel
When access token is used it is getting overriden along with any other query parameters causing 401 error. On signalr_client side this error is not handled properly and nothing happens until handshake timeout is triggered in HubConnection.
There are no stop mechanism in sse_channel so when .stop() method is called on instance of HubConnection the underlying sse connection continues to exist and receiving server sent events leading to unwanted behavior.
If anyone encounters same issues I've made a workaround for them in here.
@sefidgaran I'd be glad to help resolving these if you can suggest a solution on how to deal with sse_channel. The package itself seems to be abandoned so I'm not sure if opening PR there would work.
When using Server Sent Events transport there are at least 2 issues caused by underlying implementation of sse_channel
If anyone encounters same issues I've made a workaround for them in here.
@sefidgaran I'd be glad to help resolving these if you can suggest a solution on how to deal with sse_channel. The package itself seems to be abandoned so I'm not sure if opening PR there would work.