Known Issues Affecting VPP App Installation & Updates for Apple Devices with 2025.1 and Above
Summary
Related SOTI ONE Platform Products
Issue Description
On SOTI 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
SOTI MobiControl version 2025.1 and above.
Symptoms
The following symptoms can help 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 or update results in no action, or only partial success after repeated attempts
- Automatic app updates to newer versions do not proceed despite policy settings
- App deployment fails despite sufficient licenses being available in ABM
Prevention
N/A
Cause
SOTI is addressing the following causes:
- Database corruption (duplicate key entries) that cause failures in license association
- Apple VPP API rate limiting (HTTP 429) that interrupts token refresh and license reconciliation
- SQL constraint violations that prevent reliable app catalog synchronization and automatic app updates
Issue Resolution
N/A
Workarounds
The following workarounds are available while the issue is being addressed:
- Trigger manual device check-ins via the 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 some cases is currently being validated and will be deployed once testing is complete.
Was this helpful?
Thanks for your feedback