Forum Discussion
Devices not receiving managed configuration after enrollment
My team uses Android Management API to manage our enterprise's devices. Our management policy includes managed configurations for our Kiosk application, in order to correctly enroll our devices into our services. If this is not done, device provisioning fails.
Over the past few months (first report we received was on January 13th), we have observed that certain devices are failing to receive the managed configurations, and thus fail to go through the process correctly. They fail to receive configurations on a policy change as well, which affects our existing devices.
Before, removing the devices from our policies and enrolling again would succeed in sending the managed configurations to the affected devices. However, this issue is now persisting across attempts and happening more frequently. We have devices affected on both Android 13 and 14.
Might be related to this topic: Managed configuration not getting pushed onto some devices in work profile | Android Enterprise Customer Community - 10285
According to the support team, the global fix is currently rolling out and should be completed on the 15th of April.
I had also raised similar issue like a year ago, In my case the managed configuration is null when the require for setup application tries to get using the RestrictionsManager in work profile, so far no solution.
Might be related to this topic: Managed configuration not getting pushed onto some devices in work profile | Android Enterprise Customer Community - 10285
According to the support team, the global fix is currently rolling out and should be completed on the 15th of April.
