Android Enterprise APK app configuration returns empty RestrictionsManager bundle after Generic Android enrollmentSolved

Participant
Discussion
3 days ago Jun 24, 2026

I’m testing managed app configuration for an in-house Android APK deployed through Hexnode. The APK is added as an Enterprise app, and I uploaded the app configuration JSON in the policy.

Hexnode shows the key-value pair correctly. The app has android.content.APP_RESTRICTIONS metadata and an app_restrictions.xml file with the config key declared. But inside the app, this still returns an empty bundle: RestrictionsManager.getApplicationRestrictions() Is app configuration only supported for Managed Google Play apps, or should this also work with Enterprise APKs?

Replies (1)

Marked SolutionPending Review
Hexnode Expert
3 days ago Jun 24, 2026
Marked SolutionPending Review

Managed app configurations are not limited to Managed Google Play apps. Hexnode supports managed configurations for Enterprise APKs as well, provided the app includes the required restrictions metadata and the configuration JSON is uploaded correctly in the policy.

However, the enrollment type is important here. If the device is enrolled using Generic Android, it uses the legacy Android Device Administrator management mode. Device Administrator enrollment does not support delivering app restrictions to apps through RestrictionsManager.

For RestrictionsManager.getApplicationRestrictions() to return the configured JSON values, the device must be enrolled using Android Enterprise. After re-enrolling the device through Android Enterprise and applying the policy again, the Enterprise APK should be able to receive the configured bundle.

Regards,
Mary Romero

Save