iOS required app update not pushing automatically until policy is edited and savedSolved

For iOS apps deployed through a Required Apps policy, Hexnode can push available app updates automatically, but the update is triggered when the device receives a sync/update command.

Common actions that trigger this include:

– Running a manual Scan Device action.

– Running a manual Scan App action.

– Deploying, editing, or saving the associated policy.

Hexnode also performs scheduled device scans automatically, but these occur once daily. If the app update became available after the device’s last scheduled scan, the device may not receive the app update command immediately.

In your case, editing and saving the policy refreshed the policy deployment and triggered the update command, which is why the app update started initializing on the iOS devices after that.

Regards,
Mary Romero

So if an App Store app update appears during the day, the devices may wait until the next scheduled scan unless I manually scan the device/app or save the policy again?

Yes, that is correct. The app update does not necessarily push at the exact moment the new version becomes available in the App Store or in the app inventory. The devices need to receive the update command through a sync event. If you need the update to go out sooner, you can trigger it manually by using Scan Device or Scan App, or by refreshing the policy by editing and saving it. Otherwise, the update should be picked up during the next scheduled daily scan.

Regards,
Mary Romero