(short issue description)Only the error code but no error reason was returned after the MQTT5 connection failed.

[powerzd]

Describe the bug

My client encountered an error code 2065 during the MQTT connection process. The failure callback did not return the error reason simultaneously, and I have no idea how to resolve this issue. I want to know how to handle this error and also need a documentation that explains all the connection error codes.

Expected Behavior

Both the error code and the error reason can be returned.

Current Behavior

When the error code 2065 is encountered, only the error code is returned, and no error reason is provided.

Reproduction Steps

It occurs when I encounter the error code 2065.

Possible Solution

No response

Additional Information/Context

No response

SDK version used

1.27.2

Environment details (OS name and version, etc.)

Android 16 SM-S928U

[bretambrose]

2065 is https://github.com/awslabs/aws-c-http/blob/main/include/aws/http/http.h#L35C1-L35C46. Looks like you're using websockets and the handshake with IoT Core failed. You should enable logs and capture the logs and attach them to the issue for further feedback: https://github.com/aws/aws-iot-device-sdk-java-v2/blob/main/documents/FAQ.md#how-do-i-enable-logging

[xiazhvera]

For details on getting error reason from the code, check out FAQ: https://github.com/aws/aws-iot-device-sdk-java-v2/blob/main/documents/FAQ.md#how-do-i-get-more-information-from-an-error-code

[powerzd]

Thank you all. With your help, I have identified the problem. The failure was caused by a significant discrepancy between the local time and the standard time.