iPads prompting for Apple ID when Required Apps are pushed with VPPSolved

Participant
Discussion
7 months ago Jan 18, 2026

Hi everyone. We have a batch of supervised iPads enrolled in Hexnode. When our Required Apps policy runs, the devices keep prompting for an Apple ID sign-in, but the Apple ID we have available on-site cannot be used to make app purchases.

At first, the apps in Hexnode didn’t show any VPP license count. After I manually synced VPP, some apps started showing their licenses, but the iPads are still throwing the Apple ID prompt. Additionally, a few actions like a device restart and app installations got stuck in a “Pending” state even though the devices had checked in recently.

What is the correct flow for silently installing apps on supervised iPads without asking users for an Apple ID? Do users need to be attached to the VPP apps, or is device assignment enough?

Replies (1)

Marked SolutionPending Review
Hexnode Expert
7 months ago Jan 18, 2026
Marked SolutionPending Review

Hello,

Thank you for reaching out to Hexnode Connect!

For supervised iPads, apps can be installed silently only when they are deployed using device-assignable Apple VPP (Volume Purchase Program) licenses. You do not need users to sign in with an Apple ID, nor do you need to attach VPP licenses to individual users—the license is simply assigned directly to the device itself.

If the iPads are still prompting for an Apple ID after a VPP sync, it is typically because iOS is falling back to the standard App Store method. This happens if even one app in your Required Apps policy cannot be fulfilled via VPP. Here is the recommended cleanup process to resolve this:

  1. Remove Native System Apps: Ensure you haven’t added native Apple apps (like Safari, Mail, Messages, or Photos) to your Required Apps policy. These are built into the OS, cannot be purchased via VPP, and will immediately trigger an Apple ID prompt if you attempt to push them.
  2. Verify License Counts: Navigate to the Apps tab in your Hexnode portal and confirm that every third-party app in your policy has an available VPP license count (e.g., 9/20).
  3. Re-trigger the Deployment: Once you have removed any native apps and confirmed your VPP licenses, open your Required Apps policy, click Manage > Modify, and save the policy again without making any changes. This action re-triggers the app deployment to your targeted devices.

Regarding your actions being stuck in “Pending”: Apple’s MDM framework does not allow an MDM solution to remotely wake or unlock a device on demand. If the iPads are asleep or locked, actions will remain pending. Simply unlock the affected iPads, keep them awake and connected to the internet, and run a Scan Device action from Hexnode. Once they process the updated policy, your apps will install silently.

I hope this helps streamline your app deployment! Please feel free to reach out if you have any further questions.

Best regards,
George
Hexnode UEM.

Save