Posts

Post not yet marked as solved
1 Replies
376 Views
Hi, Yesterday, we noticed that our MDM solution could no longer deploy unlicensed (ie. no VPP/App Store App License), free App Store Apps on our managed iOS devices. This affects all versions of iOS and all versions of our MDM solution. The error on the device suggests that it's looking for a App Store License (aka VPP) for that application. This, despite the fact that the InstallApplication command sent from the MDM to the device does NOT specify that the application is supposed to be (VPP) licensed. If the MDM solution is configured to use App Store App Licensing (either device-based or user-based VPP), the application gets installed successfully (after the license for the application is assigned to either the device or user). Can Apple please confirm that this is a known issue they are working on fixing? Can anyone else confirm that they've come across this issue as well?
Posted
by awcool.
Last updated
.
Post not yet marked as solved
2 Replies
337 Views
Last Thursday, some of our customers and SOTI discovered a new issue with Apple's iTunes lookup service (https://itunes.apple.com/lookup).  The issue is that Apple's iTunes lookup service sometimes erroneously returns an HTTP 404 Not Found error. Please see the HTTP request/response logs attached in the Feedback (FB8566694) raised a few days ago. This issue prevents our enterprise customers from using key features in our MDM solution that relies on the ability to search for App Store applications including: the App Catalogue Restrictions, Single App Mode, and many more profiles We have noticed that the iTunes service we use to look up both App Store and Custom/B2B apps (by Application ID) as described in Apple's MDM documentation on page 155 (”contentMetadataLookupUrl”) does not suffer from this issue.  However, as far as we can tell, the contentMetadataLookupUrl service cannot be used to search for App Store applications by a search term like Apple's iTunes lookup service can. So, we would like to understand how we can resolve this issue for our customers. Is there a more robust service we should be leveraging? Is Apple aware of this issue? If so, when will it be addressed?
Posted
by awcool.
Last updated
.