Cannot trigger 'disconnected' event when client connect fails

[mrcoon]

The default state of the client is 'DISCONNECTED'. When the client has failed to connect, the state has not changed and the 'state' event cannot be triggered. As a result, the corresponding operation cannot be performed when the client is disconnected.

[samlin08]

It also occurs to me, i have added all the events to client instance which list behind the State Part connected, connectedReadOnly, disconnected, expired and authenticationFailed. not any event has been triggered after connect failed. The error come from a wrong server ip. In this case may still need a trigger for error handling .

[rramk]

Same here, it happened with an invalid server. can we get a fix for this? @alexguan