Hi, I created a same issue before(#69), in which you suggest me to upgrade to new version of 3.2.0.

Unfortunately, this issue persists even if we are using 3.2.0 now.

As the screenshot and loggings said, the SocketClosed will always happen after a token is expired, even if there is already at least one token refresh got happened.

Is it an expected behavior? It looks strange, since there should be a token refresh periodically and the old token should not be used anymore. But it looks like the old token is hold and cause connection exception finnally.