Android devices inactive in Hexnode with compliance warnings after app update pendingSolved

Hi @thomas_m ,

Android devices are marked Inactive when they have not checked in with Hexnode for the configured inactivity period. This usually indicates that the device is not communicating with the Hexnode server.

Common causes include:

• The device is offline or has restricted network access.
• The Hexnode app or required managed app is outdated, disabled, or not functioning correctly.
• Battery optimization or background restrictions are preventing communication.
• The device was factory reset, unenrolled, or is no longer actively used.
• A policy compliance requirement is failing, such as a required app version not being installed.

The expired APNs certificate notification does not affect Android device management. APNs is used for Apple device communication, mainly iOS, iPadOS, and macOS. Android devices rely on Android/Google services and the Hexnode agent for management communication.

For the compliance warnings, check the warning details on an affected device. If the warning is related to an app version, update the app from the managed Google Play Store or remove the outdated build and install the latest available version. Once the device checks in again, the status and compliance information should refresh in the portal.

Regards,
Isabel Lora
Hexnode UEM

Had a similar thing happen with a managed Android app. The device itself was enrolled, but the old app version kept triggering compliance warnings. Updating the app through managed Google Play cleared the warning after the next device sync.

@ed_evans , if the compliance warning is tied to a required or managed app version, installing the current version should clear the warning after the next successful device check-in.

To reduce recurrence:

Keep managed Google Play apps updated in the Hexnode app inventory.

Confirm that affected devices can access Google Play services and Hexnode services.

Avoid restricting background activity for the Hexnode app.

Use app update policies where possible instead of relying on manual updates.

Periodically review devices that have not checked in for several days and trigger a sync when they come online.

If Android devices continue to remain inactive even after the app update and a successful network connection, the next area to check would be device communication restrictions or whether the Hexnode app is still active on the device.

Regards,
Isabel Lora
Hexnode UEM