The server actively disconnects, the SDK cannot perceive(SDK v4.0.4beta)

[MrZhuGe]

Hello, I found a problem during the use. I use the SDK connection service on one device, and use the same device information connection service on the other device. The server will actively disconnect the first device, and then the SDK does not sense it and does not give it. Any callback information is blocked on the heartbeat. In previous versions of the SDK, it was able to detect that the server was actively disconnected.

[MrZhuGe]

@gordonwang0 I think that the server actively closes the connection of the device, there should be a disconnect callback, right?

[gordonwang0]

Hi @MrZhuGe,

You are correct, currently server-to-client disconnects are not reported through the disconnect callback. We will consider implementing this shortly.

[gordonwang0]

By the way -- it is expected for your application to block until the MQTT keep-alive, as that is how MQTT can detect the server-side closed connection. Any other ways to detect a server-closed connection, while possible, are outside of the MQTT spec.

[MrZhuGe]

It is convenient to ask about the handling of this problem. We are using it. This issue has a relatively large impact on us, thank you.

[abhidixi11]

I have created internal issue to track this feature request.

[MrZhuGe]

@abhidixi11 @gordonwang0 Excuse me, is there a solution to this problem?

[lundinc2]

Hello @MrZhuGe,

We currently have not implemented this feature yet. In the meantime, would it be possible for you to use the MQTT keep alive mechanism described earlier by @godonwang0 in your application?