Error from package update: "The installed criteria is not met. The current update was not installed on the device" about iot-hub-device-update HOT 3 CLOSED

Hello, it appears you are attempting to import a .deb file directly to the Device Update service, then deploy it to your device. This is the workflow we support for image-based updating, but our package-based update flow is slightly different.

Package-based updating requires the user to first host the .deb package on a Linux package repository that is part of their on-device package manager's sources list. Then the user should import an APT manifest file to the Device Update service, not the .deb package itself. When a package-based update is deployed to a device, the APT manifest file is downloaded onto the device and the APT handler uses this to then get the .deb package from the appropriate repository and install it.

If the user desires to import and deploy a .deb package directly using the DU service (without hosting the package on a Linux package repository), then the user must also create their own on-device handler to install the package, and change the "updateType" field in their import manifest accordingly.

Additional information about the Import step and the package-based updating workflow can be found here: Introduction to Device Update for Azure IoT Hub | Microsoft Docs. For an example of an APT manifest file, see here.

from iot-hub-device-update.

Hi @chrisjlin , thank you for reply. You have confirmed for me that the idea of Device Update I had in mind isn't how Azure's DU works.

I question Azure's design for doing updates using APT packages.
In Import Update screen, you ask for a manifest file, a collection of files to include in the update and a Storage Account directory. Importing this update actually gives Azure everything that it needs to install an update on the device.
So, why would you still require your users to host the .deb package on a Linux package repository first?

from iot-hub-device-update.

@mlagridigital Thanks for the feedback! We have updated our import process with our Public Preview refresh release to make it easier to upload import manifest and files. Please take a look at the updated docs here. Device Update apt manifest
Currently, Device Update delivers package-based updates from existing Debian repositories and does not have its own built-in Debian repository. Customers could choose to deploy their own Debian repository (i.e. Debian repo setup).

We are evaluating built-in Debian repository support for a future release of Device Update.

from iot-hub-device-update.