I have a Mandatory Apps policy that includes a managed Google Play web app. It installs fine on most Android devices, but a couple of devices did not get the web app automatically. When I checked the policy, the devices appeared under Policy Targets, but the app still wasn’t installing. One of the devices had also been removed and re-enrolled, so I was seeing an older device name in the target list and wasn’t sure whether the policy was actually associated correctly. What is the right way to refresh or push the policy so the web app installs?
10 Views
Replies (4)
Marked SolutionPending Review
Hexnode Expert
8 hours ago
Jun 03, 2026
Marked SolutionPending Review
For Android managed Google Play web apps assigned through a Required Apps policy, first confirm that the policy is still associated with the intended device or device group. If the device appears in the target list but the app is not installing, refresh the policy association by re-saving the policy:
- Go to Policies.
- Open the affected Required Apps policy.
- Click Manage.
- Select Modify.
- Without necessarily changing the configuration, click Save.
This re-applies the policy and refreshes the target association. After saving, go to Manage > Devices, open the affected device, and check Action History to confirm that the Required Apps policy shows as associated. Once the policy association is successful, the managed Google Play web app should be pushed to the device automatically
Marked SolutionPending Review
Participant
5 hours ago
Jun 03, 2026
Marked SolutionPending Review
That was the part I was missing. I opened the policy but wasn’t sure whether I needed to use the target association option again or just edit the policy itself. After going to Manage > Modify > Save, the device status showed that the Required Apps policy was associated a couple of minutes later.
Marked SolutionPending Review
Participant
3 hours ago
Jun 03, 2026
Marked SolutionPending Review
I’ve run into something similar when a device was re-enrolled and the old device name still made the policy target list look confusing. Re-saving the policy forced Hexnode to evaluate the current target association again, and the required app deployment kicked in after that.
Marked SolutionPending Review
Participant
2 hours ago
Jun 03, 2026
Marked SolutionPending Review
Confirmed, re-saving the policy fixed it. The policy association now shows as successful on the device, and the missing web app installed automatically.
Save
