Error while saving any changes in edge manifest in IOT central.

Question

Error while saving any changes in edge manifest in IOT central.

Priyanshu Aggarwal 25

Recently, I have been facing issue regarding edge manifest in IOT central. Whenever any changes needs to be done by edit manifest option, it pops up an error when I try to save it.

The error I get:
"

Problems loading reference 'https://json.schemastore.org/azure-iot-edge-deployment-2.0.json': Unable to load schema from 'https://json.schemastore.org/azure-iot-edge-deployment-2.0.json': Failed to fetch.(768)

"

Accepted answer

0 additional answers

Your answer

Answer 1

Sander van de Velde | MVP 36,766 MVP Volunteer Moderator

Hello @Priyanshu Aggarwal

welcome to this moderated Azure community forum.

Can you elaborate on what you mean with 'edit manifest option'?

If this is done in the portal using the UI, there seems to be something broken.

In that case, create an Azure support ticket so the backend an be inspected by the support team.

UPDATE AFTER DISCUSSION

It seems the User Interface experience in the portal is deprecated.

The product team is engaged to fix this.

Either uploading the full manifest (edited outside the portal) or using CLI commands are a workaround.

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.

Priyanshu Aggarwal 25 Reputation points

2025-06-19T09:14:14.14+00:00

I am experiencing an issue with the "Edit Manifest" or "Edit JSON" option in Azure IoT Central. When I try to save changes to the manifest (sample manifest), I encounter an error. This problem has started occurring recently, within the last month. The error message indicates a problem with loading the schema from the specified URL.

Could you please help me resolve this issue?
VSawhney 715 Reputation points Microsoft External Staff Moderator

2025-06-19T11:32:39.25+00:00
Hello Priyanshu Aggarwal,

Here are some steps and insights to help you troubleshoot and potentially resolve the issue:

Schema Store Availability: The schema URL (json.schemastore.org) is externally hosted and occasionally experiences downtime or connectivity issues. You can verify its availability by opening the URL directly in your browser. If it fails to load, the issue is likely external and temporary.

Validate the Manifest JSON: If the manifest JSON has any errors or is malformed, it may cause issues. You can use JSON validation tools to check for syntax errors in your manifest.

Network Restrictions: Ensure that your network or firewall settings allow outbound HTTPS traffic to json.schemastore.org. If you're behind a corporate proxy, it might be blocking access to external schema sources.

Clear Browser Cache: Occasionally, cached data can cause issues. Clear your browser's cache or try accessing the portal in incognito mode.

Manifest Validation: Even if the schema fails to load, you can still validate your manifest locally using tools like Visual Studio Code with the Azure IoT Tools extension. This helps ensure your JSON is syntactically correct and adheres to expected structure.

Use CLI as a Workaround: You can manage edge manifests using the Azure CLI (az iot central device edge manifest) which may bypass the UI limitations you're experiencing. This command group is in preview but can be helpful for direct manifest operations.
Reference Doc: https://learn.microsoft.com/en-us/azure/iot-central/core/howto-manage-deployment-manifests

Hope this helps!
Thank you!
Sander van de Velde | MVP 36,766 Reputation points MVP Volunteer Moderator

2025-06-19T19:30:44.0433333+00:00

Hello @Priyanshu Aggarwal

The error points to the first accolade in the manifest.

Can you check the last accolade too?

Can you also run the JSON through some JSON validator like https://jsonlint.com/ (please do not test with secrets in the JSON).

Do you keep these deployments manifests under version control, like GitHub? In that case, you could 'roll back' to the previous version.
Priyanshu Aggarwal 25 Reputation points

2025-06-20T06:16:05.68+00:00

Hello @Sander van de Velde | MVP

I validated the JSON file using a JSON validator, and it appears to be correct. I've been using this Edge manifest for quite some time without any issues. However, the problem seems to have started recently. Based on @VSawhney earlier point about UI limitations, I believe that’s what's causing the issue.

When I upload the manifest directly from the device, it gets validated and uploaded successfully. The issue only arises when I try to make changes to the Edge manifest directly through the IoT Central UI and attempt to save it.

As a workaround, I’ll continue uploading the manifest manually for now instead of editing it through the UI.

Share via

Error while saving any changes in edge manifest in IOT central.

0 additional answers

Your answer