Hi Richard,

If you see here https://github.com/aws/aws-iot-device-s ... C/releases, last stable release was from 2018 time-frame. We typically move to newer releases as and when they are available upstream.

Mahavir

Hi Jsam, I was not able to reproduce this issue at my end. - Example used was one from https://github.com/espressif/esp-azure/tree/master/examples/iothub_client_sample_mqtt - SDK Configuration had `CONFIG_NEWLIB_NANO_FORMAT=y` - Tried with both ESP-IDF latest master and v4.1-Beta2 release Could you ...

Please find instructions for getting started guide for Amazon FreeRTOS on ESP32 at https://docs.aws.amazon.com/freertos/la ... essif.html

What do you mean by SNI support? If this means Sever Name Indication then answer is yes, it is supported.

Hi @i-snore Is your problem solved with https://forums.freertos.org/t/missing-esp-http-client-component/9098/6? For issue regarding backtrace decoding: /Users/vp/esp/Pebble_ESP32_Firmware/build/esp32_app 0x400d6f75: [Errno 2] No such file or directory Can you please confirm as why your executable is...

When you get AWS qualification, have you ever pass IDT test? Yes, I am attaching IDT report summary for your reference ESP32_DQP.zip For IDT setup related issues you may file query at https://github.com/aws/amazon-freertos/. Interim, any specific reason why you would like to run IDT at your end?

For platform to be listed in device catalog, it must successfully cover all qualification tests. If you would like you may verify results by following setup guides listed at https://github.com/aws/amazon-freertos/tree/master/doc for any of qualified ESP32 platform.

Following code snippet from `advanced_https_ota_example` should help here: while (1) { err = esp_https_ota_perform(https_ota_handle); if (err != ESP_ERR_HTTPS_OTA_IN_PROGRESS) { break; } // esp_https_ota_perform returns after every read operation which gives user the ability to // monitor the status...

Is it possible to share more information, especially server configuration, data format (chunked or non-chunked)? Additional information to help us reproduce this at our end would be very useful.

I want to permanently change to use 4.0 IDF (from 3.3.1) as soon as I can for my project. But in order to do so, I would want 2019r2 toolchain included automatically when using install.sh/export.sh. It should not require manual patching. Do you think this will be the case by the time 4.0 is officia...