Azure Sphere SDK: When does the running OS allow a new OS update to be deferred by the application.

Question

I have read through the documentation for Azure Sphere OS update deferral by the application and it is not clear how the running OS decides when to allow the application an opportunity to defer an OS update.

The specific scenario is an Azure Sphere enabled product that is offline (in a box on a shelf). While the product is offline, Microsoft releases a new Azure Sphere OS update. Two weeks later the product is brought online. The running OS determines that there is an OS update.

Will the running OS allow the application to defer installation of the new OS update?

Or will the OS update be forced (no opportunity for deferral) since it has been two weeks since the OS update was released?

Answer 1

Hello,

Thank you for posting the question!

The deferment API limits start from the time that the device is made aware of the update requirement. In the case you outline below, the offline device will come online, realize there is an OS update, consult the application (if it has registered for deferment notifications), and allow the application to defer the update for up to 24 hours.

This API is designed for applications to ensure the device is in a "safe" state before update begins, which is why the period starts from the time the device is aware of it.

Hope this answer helps. Please let us know if you have any questions.