Describe the bug
When I try to connect to the AWS using AwsIotMqttManager and the device time is out of sync, I'm getting the 403 response. Setting time offset using SDKGlobalConfiguration.setGlobalTimeOffset() doesn't affect this.
To Reproduce
Which AWS service(s) are affected?
AWS IoT
Expected behavior
Adding the global time offset should work with IoT
Environment Information (please complete the following information):
Additional context
It seems that AwsIotMqttManager uses System.currentTimeMillis() when generating the signed AwsIoT websocket url.
Hi @slomin ,
I'm marking this as a feature request because we might not have this ability. I have tagged @desokroshan to investigate further.
@slomin This has been fixed in the latest release 2.12.7. Could you please update to the latest and confirm. Thanks!
It works now, @desokroshan thank you for the quick fix!
Good to hear that. Thanks for the confirmation!