DMM App Managed doesn't allow for reinstalls or respects version element

Hello, this may not be the correct place to ask this question so I apologize in advance if this is the case.

I am currently running into two specifc issues while continuing to implement the app.managed configuration which are quite frustrating and I will detail them below

  1. Unlike MDM where an application could be "reinstalled", by sending an install application command down for the same app DM does not have a similar mechanism which causes some issues as (while inconsistent) devices do not always respect the configuration sent down, and will not begin downloading VPP applications. They can be seen in the configuration when checking under VPN & Device Management but they do not return on a status report, alternatively and app will "install" but will have a cloud symbol next to it requiring a download (which I believe would be impossible on supervised devices without apple accounts/have restricted apple accounts associated to them). These apps are also reported incorrectly, as they return a managed response while being inaccessible. Both of these issues are solved by removing and reinstall applications (occasionally). Is there any easier way to trigger a re-install or is this the only way to trigger this?

  2. The Version element that can be optionally sent down does not seem to work (or if it does, does so inconsistently). A device will very happily download the application initially with the version element present, though when we detect an updated external ID from the VPP program and send down an updated configuration devices behave unexpectedly. Some have ignored it, some have responded back that a download has begun (with no download taking place and the application clearly still being the initial installed version as can be see in the apps page) or it just works, but there is not consistency. I realize a new UpdateBehavior object has been added to possibly handle this, but it is only supported in iOS 26 and above and there are plenty of people who do not have phones that can upgrade that far. Are there alternative ways to enforce an application update other than uninstalling and reinstalling the application without the version (or will sending down a config without a version after one was originally pinned force it to update to latest?)

Kind Regards

A quick follow along, the version key seems to be much more temperamental on iOS versions 18.7 and below (from my limited testing) iOS 26 does seem to respect it, though it does seem to be slow with the updates themselves (possibly 1 hour between the new config being sent down and the update, but that may be down to wifi/battery saver mode)

DMM App Managed doesn't allow for reinstalls or respects version element
 
 
Q