Steve Hamblett

Whatever output this is doesn't show why 'the client is not trying to reconnect even though auto-reconnect is enabled' it just shows that something called _connectionStatus doesn't match connectionHandler!.connectionStatus for...

Sorry for the late response I've been on hols. Your thinking is correct, what your seeing is a 'closure' effect in Dart, the code has closed over the old(connection A)...

OK, I've added an update for this, I've also written a test for it which seems OK but this is a tricky area. The package has been re released at...

OK so the bad state exception has gone as expected. I can tell what the reason for the auto reconnect after 5 seconds is from your log, I'll need a...

Could you supply the raw Uint8List so I can instigate further.

This is what I'm seeing when converted to JSON. [jsonconverted.txt](https://github.com/user-attachments/files/16011727/jsonconverted.txt) Is this what you expect? If not what do you expect? Its different to what you posted above but this...

Ok it looks as though the decoder thinks that the 'data' key value is encoded in base64URL due I think to the presence of a tag value of 72 in...

OK, the above was a bug in the package, it was assuming that without a hint the encoding was base64Url, this is incorrect. I've changed this now to be base16,...

I see what you are saying but I'm not seeing this behaviour, here's the log from the mqtt_server_client example with the async sleep time raised to 240 seconds. ``` /home/steve/Development/google/dart/dart-sdk/bin/dart...

Strangely in your log above you are setting the keepAlive in the connect message to 60, this will enable the broker behaviour you are seeing, i.e. after no control packets...