Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
We use WICED SDK 3.5.2 to implement an IoT device which communicated with our backend through Azure IoT Hub (MQTT over TLS).
Since today morning, all our devices went dark. Looking more closely in the WICED application what I can observe is that after a few iterations of SSL handshake, a call to function ssl_handshake_client_async() results to a crash and a restart of the application.
The problem is easy to reproduce, since the only think you need is to target the secure_mqtt sample application to an active Azure IoT Hub instance. Please find attached the log from the execution and crash of the secure_mqtt example project.
If you want a live Azure IoT Hub instance to try it out, I am happy to assist.
I must note that other MQTT clients, like MQTT.fx, operate as expected.