iOS VPP app update delay after new App Store releaseSolved

Hey @sammyy,

If the app is already assigned as a Required App, you do not need to remove, re-add, or modify the policy for a normal App Store version update.

For VPP apps, a delay after release is expected. Hexnode checks Apple for VPP app updates on a scheduled cycle, typically once per day around 7:00 AM UTC, and schedules update pushes around 10:00 AM UTC for devices where the app is assigned as required.

The final installation timing can also depend on Apple’s VPP deployment behavior and device-side conditions, such as:

• The device being powered on and online.
• Network access to Apple services.
• Wi-Fi/cellular connectivity.
• The app not being actively blocked from updating by device state or network restrictions.

So, if Hexnode already shows the latest app version in the app inventory, the update has been detected correctly. The remaining version difference on devices is usually part of the normal staged rollout.

Regards,
Isabel Lora
Hexnode UEM

That makes sense. I checked the app entry in Hexnode and it does show the new version there. The confusing part was that only one device updated while the rest stayed on the previous build.

I’ve seen this with VPP apps too. It usually catches up later, especially if the devices are not all online at the same time. Running an app inventory scan helped us see updated versions sooner on a few devices.

Yes @abel-j, if you need to speed up visibility or prompt a refresh for specific devices, run the Scan for Apps remote action on those devices periodically. This refreshes the app inventory reported back to Hexnode and can help confirm whether the update has installed.

A practical checklist would be:

1. Confirm the app’s latest version is visible in Hexnode under Apps > Local Apps.
2. Ensure the app is still assigned as a Required App through the relevant policy.
3. Wait for the scheduled VPP update cycle and Apple’s staged rollout to process the update.
4. Run Scan for Apps on priority devices to refresh app inventory reporting.
5. If devices remain on the old version after 48–72 hours, review device connectivity and app update restrictions.

In this case, since the latest version was already visible in Hexnode and the app was assigned as required, no policy change was needed. The delay was due to the normal VPP update cycle and staged deployment behavior.

Regards,
Isabel Lora
Hexnode UEM