Android kiosk devices non-compliant due to missing Required AppsSolved

Participant
Discussion
2 days ago Nov 06, 2026

Some of our Android tablets in kiosk mode are showing out of compliance because of missing mandatory apps. The apps listed include Hexnode Remote View and codes.simen.l50notifications. When I try pushing the app from the policy, it does not complete on a few devices, though other tablets are fine.

One affected model is a TCL 8 Plus. I removed Hexnode Remote View from the Required Apps policy, but I do not see any uninstall event in the action history, and the compliance error has not cleared yet. What is codes.simen.l50notifications, and what is the correct way to clear this missing app compliance status?

Replies (2)

Marked SolutionPending Review
Hexnode Expert
2 days ago Nov 06, 2026
Marked SolutionPending Review

Hi @felixfrost ,

For Android kiosk devices, missing required app compliance is usually tied to the apps configured under the policy’s Required Apps list.

In this case, there are two separate points to check:

1. Hexnode UEM Remote View compatibility
Hexnode UEM Remote View is intended for Samsung Knox-supported devices. A TCL 8 Plus is a non-Knox Android device, so Hexnode UEM Remote View should not be kept as a required app for that model. If it remains in the Required Apps list, deployment can fail and the device may be marked non-compliant.

2. codes.simen.l50notifications
codes.simen.l50notifications is the package name for a third-party app called Heads-up Notifications. If this package is listed as a required app but is not installed on the tablet, Hexnode UEM will continue to report the device as non-compliant.

To clear the missing app compliance alert:

  • Go to Policies.
  • Open the Android kiosk policy assigned to the affected devices.
  • Click Modify.
  • Navigate to Android > App Management > Required Apps.
  • Remove codes.simen.l50notifications if the app is no longer required.
  • Also remove Hexnode UEM Remote View from the same list for non-Knox Android devices if it is not compatible with that model.
  • Save the policy.

After saving the policy, run both actions on the affected devices:

  • Scan Device
  • Scan Applications

Then refresh the device details page and check the compliance status again.

Regards,
Isabel Lora
Hexnode UEM

Marked SolutionPending Review
Participant
2 days ago Nov 06, 2026
Marked SolutionPending Review

That explains part of it. I had removed Hexnode UEM Remote View, but I did not remove codes.simen.l50notifications. I was expecting an uninstall action to appear after removing the app from the policy, but nothing showed up in the action history.

Save