Andrey Demidov

The same exception on 8.1.0 and CryptoExchange.Net 5.1.10. I see CloseInternalAsync call "_ctsSource.Cancel()" and doesn't check what it was Disposed. I can't enable the Debug mode logs because every data...

I'm tried to call socketApi.UnsubscribeAllAsync() before call socketApi.Dispose but exception was the same. Library used disposed CancellationTokenSource .

The problem isn't disposing socket API. 8.0.11 version is working fine without unhandled exceptions ---> call UnsubscribeAllAsync 21:41:40.65[5163]DEBUG:[BinSpotV1] API: 2022/05/27 21:41:40:660 | Information | Binance | Socket 38 Cancellation token...

Hi, it was set. It happens if connection was lost

release 7.2.6 execution - net 6.0

Additional logging was disabled. Connectionlost/restored handling has only SubscribeToUserDataUpdatesAsync stream. if connection lost will be initiated full reconnection (new BinanceSocketClient will be created).

It disposes the BinanceClient and BinanceSocketClient and makes new instances.

Because it was written before reconnection handling appeared, and worked fine some years.

And it disposed not on ConnectionLost. It disposed if some abnormal error was happened. For example, invalid listen key in KeepAliveUserStreamAsync call.

Can I use WriteApi for multi threads?