Error with manifest upload

Question

I'm attempting to do utilise the ADU service for OTA updates, and I am getting this error with my manifest file:

A problem occurred trying to parse the schema for one or more import manifests. Delete the file or adjust its syntax, and try again.Learn more Contoso.ESP32-Azure-IoT-Kit.1.1.importmanifest.json

I have been using the IoT middleware for freertos repo, in which they describe an az command to use in powershell:

az iot du update init v5 --update-provider Contoso --update-name ESP32-Azure-IoT-Kit --update-version 1.1 --compat deviceModel=ESP32-Azure-IoT-Kit deviceManufacturer=ESPRESSIF --step handler=microsoft/swupdate:1 properties='{"installedCriteria":"1.1"}' --file path=./azure_iot_freertos_esp32-v1.1.bin > ./Contoso.ESP32-Azure-IoT-Kit.1.1.importmanifest.json

I haven't had a problem in the past (around 5 device update trials) and now every time I try I get this error. I've tried creating it using my own cmd, azure cloud shell, and the azure service for creating manifests itself. But I keep getting the same error. Please can someone help? I've attached the manifest file I am trying (in txt format). manifest.txt

Answer 1

Thanks for posting your question in the Microsoft Q&A forum.

Make sure your manifest file is valid JSON. You can use online JSON validators to check for any syntax errors and ensure you're using the latest supported schema version for Device Update for IoT Hub. As of now, the latest version is typically 4.0.

Verify that the compatibility properties match the format expected by Device Update for IoT Hub.

Make sure the installedCriteria is a string value that can be used to determine if the update is installed.

---

Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful

Answer 2

Hello @Ben Hobbs,

welcome to this moderated Azure community forum.

Because it looks like something changed on the backend of the IoT Hub, I suggest opening an Azure support ticket so the team can check what is happening over there.

Please share the outcome here so others with the same problem benefit from this answer too.

---

If the response helped, do "Accept Answer". If it doesn't work, please let us know the progress. All community members with similar issues will benefit by doing so. Your contribution is highly appreciated.

Answer 3

This seems to have been fixed. At least for me.