Android Enterprise required apps not installing when allowlist policy is enabledSolved

Yes @matteo. With Android Enterprise Device Owner deployments, a very restrictive allowlist can sometimes block components that Managed Google Play needs in order to install and update apps.

In addition to allowing your business apps, make sure components required for Android Enterprise app deployment are not blocked. In particular, verify that:

• Google Play Store and Managed Google Play services (com.android.vending) are allowed.
• Android Enterprise management components such as Android Device Policy/CloudDPC are not being restricted.
• Any dependencies required by your business apps are also available.

Also, if you’re using an allowlist policy, each app should be:

1. Added under Required Apps, so Hexnode knows it should be installed.
2. Included in the allowlist, so it isn’t blocked after installation.

Regarding the Samsung tablet where the Hexnode app appears stuck in an Initiated state, that can sometimes happen if the device is restricting background activity. In addition to restarting the device, I’d recommend:

• Running Scan Device and Scan for Apps from the device page.
• Verifying that the Hexnode app has all required permissions.
• Checking whether battery optimization or power-saving settings are restricting the Hexnode app.
• Confirming that the device has network connectivity and is communicating with the portal.

These steps usually help determine whether the issue is related to app deployment, policy restrictions, or background synchronization.

Best Regards,
Isabel Lora
Hexnode UEM

I ran into something very similar with Android tablets. The apps were listed as required, but the allowlist was too strict, so the Play Store components couldn’t finish the installs. Temporarily relaxing the allowlist helped confirm it was a policy issue rather than an app deployment problem.

That makes sense. I had the business apps in both Required Apps and the allowlist, but I don’t think I had the Play Store service package or Android Enterprise management components allowed. After adding those and running Scan Device followed by Scan for Apps, the missing apps started coming through.

For the Samsung tablet, checking battery optimization and permissions turned out to be the missing piece. Once I adjusted those, the Hexnode app started syncing normally again.

One extra thing I noticed after the apps installed: links from Outlook were opening in Chrome instead of launching Bluebeam directly. Changing the Hexnode allowlist didn’t seem to affect it. It felt more like the way Bluebeam handles Android links.

That sounds consistent with how Android handles app links.

Hexnode can deploy and restrict apps, but it doesn’t control how a third-party app processes links. If a link from Outlook opens in Chrome instead of directly launching Bluebeam, the behavior is usually determined by:

• The link-handling capabilities supported by the Bluebeam app.
• Android’s default app settings.
• The app’s own configuration.

To confirm whether this is application-specific, try reproducing the behavior without restrictions in place. If the result is the same, it would be best to check with the Bluebeam vendor regarding supported link handling.

Best Regards,
Isabel Lora
Hexnode UEM