iOS VPP app compliance shows missing app count but no missing apps foundSolved

Hello,

Thanks for reaching out to Hexnode Connect.

This behavior can occasionally happen when VPP app assignments, device inventory scans, and the portal’s compliance evaluation do not all update at the exact same time. If an app is already successfully installed on the device but Hexnode still reports a missing app count, the inventory and compliance state simply needs a moment to catch up.

If you run into this stale communication state again, here is the recommended sequence to force a refresh between the iPhone, Apple services, and the Hexnode portal:

A. Force a Device Sync

1. Go to Manage > Devices and open the affected iPhone.
2. Click the Actions dropdown.
3. Under Scanning & Monitoring, run Scan Device, and then run Scan for Apps.
4. Check the Applications tab on the device page to verify that no apps are genuinely missing or pending installation.

B. Refresh the Policy

If the compliance mismatch remains after scanning, refresh the policy association:

1. Open the policy associated with the iPhone.
2. Click Save again without making any actual changes.
3. Go back to the device page and run Scan for Apps once more.

C. Reinstall the MDM Profile (If still stuck)

If the device status is still stubbornly non-compliant after the above steps, re-downloading the management profile can clear out any stale communication states (note: this will not remove your existing policy configurations):

1. Open the Hexnode UEM app on the iPhone.
2. Tap the menu icon, and under Other, choose Re-install MDM profile.
3. Complete the profile download through Safari.
4. Go to Settings > General > VPN & Device Management on the iPhone.
5. Select the newly downloaded Hexnode management profile and install/reinstall it.
6. Return to the Hexnode portal and run Scan Device and Scan for Apps.

After completing these steps, just allow a little time for the device, Apple’s VPP services, and the Hexnode portal to finish syncing. Once the evaluation completes, the device will return to a compliant status.

I hope this helps you resolve any future compliance sync delays! If you find any more issues or need further assistance, feel free to reach out.

Best regards,
George,
Hexnode UEM