@Systems Engineer Thank you for you quick reply. I understand how to investigate the issue at first. However no way to print raw MDM push token value? Even after we got the SHA256 value of the MDM push token different from the one the MDM server stores, it is not so useful for us. If we could know the latest raw token value from sysdiagnose or somewhere, we can recover the push error by updating the token value on MDM server DB, and customers' claim can be reduced. Thank you.

https://developer.apple.com/help/account/manage-service-configurations/apps-and-books-for-organizations/ I didn't find it but Official reference is provided.

{ "Identifier": "389459bf-0902-58dd-be0e-11c83c695a8b", "Type": "com.apple.configuration.app.managed", "Payload": { "InstallBehavior": { "Install": "Optional", "License": { "VPPType": "Device" } }, "BundleID": "com.microsoft.Office.Powerpoint" }, "ServerToken": "579a665a7d243323c5ba6da85cc8a5ffa57a114e2e558ac93983ca2cad658d61" } DDM configuration payload is like this. Since I already observed that the app is auto-installed by replacing Install: Optional with Install: Require, the payload seems valid.

It seems that the playground app (MDM Agent for SwiftUI) should be installed as managed via MDM, and no need to be available in App Store. The implemented code is unchanged. The only problem is the way to distribute the playground app, for the ManagedAppDistribution to work as expected. It is still a problem... it is too hard to debug the playground app...

Is this an alternative way for iOS >=18.4? https://developer.apple.com/documentation/managedapp

@Device Management Engineer Thank you for your quick response. So is this API just alternative to iTunes Lookup API? (Even so, it's really amazing for us. Thank you for the improvement :)

@Device Management Engineer Thank you. It seems your suggestion (reloading configuration by changing ServerToken) is effective. We can check that it works as expected with Scrub Browser app. https://zenn.dev/link/comments/45b1d8bbde19b0 (sorry for Japanese article) I think most MDM vendor would hesitate to implement this feature because we have to remember whether the configuration is applied with LegacyAppConfigAssetReference at the first time or not. It is far from declarative... The improvement would be really amazing for us. Thank you :)

Hi, I also encountered and resolved the issue. It seems the client-capability response is made by user-channel MDM daemon. We can inspect it by checking if the push token is notified by the system-channel mdmdaemon.