Known Issues Affecting VPP App Installation & Updates for Apple devices with 2025.1 and above

Publish Date: SOTI MobiControl
134

Summary

SOTI is aware of issues with automatic installation and updates of mandatory VPP apps on ADE and supervised devices impacting macOS and iOS devices in MobiControl 2025.1+.

Related SOTI ONE Platform Products

SOTI MobiControl

Issue Description

On MobiControl versions 2025.1 and above, customers have reported issues with the deployment and updating of VPP (Volume Purchase Program) apps on iOS devices enrolled via Automated Device Enrollment (ADE) or supervised mode. Mandatory apps are not installing automatically, either appearing as “Unknown” or “Failed,” or do not update despite policy settings mandating the latest version. Underlying causes include failures in VPP token refreshes due to API rate-limiting, database inconsistencies resulting in license assignment errors, and SQL constraint violations during app catalog synchronization. 

Environment

MobiControl version 2025.1 and above

Symptoms

The following symptoms can be used to identify this issue:

 

  • Mandatory VPP apps fail to install automatically (showing as "Unknown" or "Failed" on devices)
  • VPP token refreshes fail or remain stuck in processing with no clear errors
  • Apple returning HTTP 429 "Too Many Requests" during token or license operations
  • Manually attempting to install/update yields no action or only partial success after repeated attempts
  • Automatic app updates to newer versions do not proceed despite policy settings
  • App deployment failures despite sufficient licenses in ABM

Prevention

N/A

Cause

We are currently addressing the following causes:

  • Database corruption (duplicate key entries) causing failures in license association
  • Apple VPP API rate limiting (HTTP 429) interrupt token refresh and license reconciliation
  • SQL constraint violations prevent smooth app catalog sync and automatic app updates

Issue Resolution

N/A

Workarounds

The following workarounds can be done during this period while we address the issue:

  • Trigger manual device check-ins via console to prompt temporary app installs
  • Manually refresh VPP tokens, and perform manual app update pushes

A DLL update that has resolved this issue in certain cases is underway for deployment once fully validated.

Was this helpful?