Android 13: Repeated “Install Application” actions for Required Apps after device scansSolved

Participant
Discussion
4 weeks ago Jul 30, 2026

We have some Android 13 devices where a managed app keeps signing users out. The app vendor cannot reproduce it outside our environment, so I’m checking whether anything in MDM could be triggering it.

In the device action history, I keep seeing entries like this for the same app:

– Scan Device — Success
– Install Application — Initiated
– Sent app configuration — Success

This seems to repeat after device scans. I’m seeing the same pattern across multiple devices, sometimes with different apps. Is it normal for Hexnode to show repeated “Install Application” actions for apps that are already installed, or could this be causing the app sign-outs?

Replies (1)

Marked SolutionPending Review
Hexnode Expert
4 weeks ago Jul 30, 2026
Marked SolutionPending Review

Hi @remi,

Repeated “Install Application” entries can be expected if the app is assigned through a Required Apps policy.

When an Android app is added as a required app, Hexnode checks and enforces the app installation during device scans. If the scan detects that the required app must be enforced, updated, or revalidated, an install action may be initiated again and recorded in the device action history.

This does not always mean the app is being freshly removed and reinstalled each time. It indicates that Hexnode is enforcing the required app state on the device.

To isolate whether this is related to the app sign-out behavior, try the following on a test device:

  1. Temporarily remove the affected app from the Required Apps policy.
  2. Allow the device to complete its next scan cycle.
  3. Monitor whether the repeated “Install Application” entries stop for that app.
  4. Check whether the app continues signing users out.

If the issue continues even after the app is no longer enforced as a required app, test the same app version on an unenrolled Android device with the same app configuration where possible. This helps determine whether the sign-out behavior is caused by the app itself or by managed deployment/enforcement.

Regards,
Sienna Carter
Hexnode UEM

Save