We have already implemented the Aktualizr D‑Bus API for user interaction. The user can accept or decline the update from our application, and we send the appropriate D‑Bus calls to Aktualizr.
However, our problem remains:
Even when we wait for user interaction on the device, the OTA backend already switches the device to “Update in Progress” as soon as the update is detected. At that moment:
-
the update has not been accepted
-
nothing is being installed or downloaded
-
we are only waiting for the user’s decision
-
but the server already marks it as “In Progress” and we can no longer cancel or replace the update
This is exactly the behavior we are trying to avoid.
What we would expect is that with the D‑Bus consent workflow, the device should stay in a Pending state until we send an explicit accept or cancel command via D‑Bus. Only after acceptance should it transition to “In Progress”.
Is this how the D‑Bus consent mechanism is intended to work?
Or is there currently no way to keep the device in “Pending” while waiting for user approval?
