This article aims to provide useful pieces of information and troubleshooting steps to ensure your app deployments and updates are properly functioning with Addigy.
General Troubleshooting Checklist
Addigy's Apps & Books integration requires communication with Apple Business Manager. The VPP token facilitates this communication, so make sure you have a valid vpp token that is up to date.
Apps & Books licenses are consumed on a per-device basis. If you do not have enough licenses, you will get an error saying no license was found.
Not all apps are universal. You can verify if an app is compatible with your device by checking the "Supported Devices" column in Policy > Settings > Apps & Books.
What Happens When My Single Location Apps & Books Token Is Spread across Multiple Policies?
A single Apps & Books Token can be used in multiple policies without issue. Doing so will allow you to use the same Apps & Books assets in multiple policies. The available licenses for those assets will be shared by the policies which use the token.
I’m Unable to Save My Apps & Books Token, What Can I Do?
If you run into the "Failed to Save, please check token" warning message, this would indicate that there isn't an Apple Push Certificate assigned to that policy just yet.
To remediate this, navigate to Policy > Settings > MDM Enrollment Profile, assign an Apple Push Certificate, and try to upload the token once more, the warning message should now be clear!
I Can’t Deploy Apps via Golive, What Can I Do?
If you find that you are unable to deploy Apps via GoLive because the "Deploy" button is grayed out, you may require more licenses. You can check your licenses by going to Your Policy > Settings > Apps & Books.
Additionally, if you find that the "Apps & Books" tab is grayed out, you most likely do not have Apps & Books set up in the policy for the device. You can check out our article Configuring Apps & Books for information on how to set it up.
How the Auto-Update Feature Works
The device performs mdm audits (~ 1 hour) in which it performs the "Application List" command. We then check the version of the app and if it needs an update. If the app is managed and auto-update is enabled in the policy, we queue up the install application command and the device should respond with the "acknowledged" status and queue the installation locally on the device.
Auto-Update Is Not Working, What Do I Do?
In the case that the auto-update does not occur, there are a few items to initially check. For starters, make sure the device is responding to MDM commands and all of the audits are up-to-date. If it is not, there may be an issue with MDM connectivity. A restart of the device may help or full re-enrollment may be necessary depending on the exact issue.
Also be sure to verify if the Apps & Books token is valid and up to date.
If those items check out, try deploying the app via GoLive to see if it successfully installs the updated version.
Behavior for Non-supervised Devices
Devices without supervision will receive a prompt when an app is deployed
If the prompt is not accepted, the app will not install on the device. Be sure to verify with your end users if the prompt was accepted, as you will still see a successful status when the install application command is sent.
How to Verify if an Application Was Installed via Apps & Books (macOS)
When troubleshooting Apps & Books deployments, it may become necessary to determine whether an application has been deployed via Apps & Books. The following command can be deployed to verify this status (change nameOfApp to the name of the application):
mdls /Applications/nameOfApp.app/ -name kMDItemAppStoreReceiptIsVPPLicensed
- An output of 1 means the application was installed via Apps & Books.
- An output of 0 means it was not installed via Apps & Books.
My question isn't here, what do I do?
If you have any questions, please do not hesitate to reach out to us by contacting email@example.com