iOS Web Clip deployment and Hexnode UEM app configuration limitationsSolved

For iOS, Hexnode can deploy managed app configuration payloads to supported applications, but there are Apple framework limitations to keep in mind.

If you are referring specifically to the Hexnode UEM app on iOS, an app configuration payload cannot be used to bypass Apple’s requirement that the user launches the app at least once. iOS does not allow MDM apps to run in the background or sync their app status until the app has been opened manually for the first time. This behavior is enforced by Apple and applies across MDM solutions.

So, while app configuration can be used where an app supports managed configuration keys, it cannot grant restricted Apple permissions or force the Hexnode UEM app to initialize silently in the background.

For the Web Clip issue, iOS Web Clips are deployed through a policy. The usual flow is:

1. Add the Web App/Web Clip to the Hexnode app inventory.
2. Create or edit an iOS policy.
3. Add the Web Clip under the Web Clip/Web App configuration section.
4. Associate the policy with the target iPad, user, group, or device group.

Web Clips are not deployed in the same way as standard store apps, so they may not appear where you expect when trying to push apps directly or add them to an app group.

That explains it. I was looking for the Web Clip under the regular app deployment options and app groups. So for iPads, it has to go out through a policy instead?

Yes, that is correct. For iOS devices, deploy the Web Clip using a policy rather than treating it like a regular app push. One additional point: if the iPads have an app Allowlist policy applied, make sure the Web Clip is also included in the allowed list. Otherwise, the Web Clip may install successfully but remain hidden on the device because the allowlist policy restricts what can appear on the Home Screen.