Apple App Store and Automatic Updates

DevelopersFileWave arecan frequentlyrequest updatingupdates applicationsfor and submitting new versions to Applemanaged App Store.Store FileWave is automatically sending requests to devices to upgrade applicationsapps when a newnewer version is available. For admins, this usually shows up as an app that keeps reinstalling or updating after device check-in, even when the assignment has not changed.

How does FileWave detect if there is an update?

For iOS 11.3 and laterlater, and macOS 10.13.4 and later:

Apple's MDM protocol returns theupdate information when FileWave requests the list of installed applications: each application willlist. provide,Each viaApp Store app can report the HasUpdateAvailable flag,flag. ifWhen anthat updateflag is available, and in this case,true, FileWave can send the device aan InstallApplication command to upgradeupdate the application (InstallApplication command).app.

For previous OS versions:

Every hour, FileWave is contactingcontacts Apple's iTunes database and updates metadata aboutfor applications used in your environment. When a device checks in for Verify, weFileWave comparecompares the application versionsversion (onreported by the device,device from iTunes) and ifwith the version from iTunes. If the iTunes version is higherhigher, weFileWave knowtreats therethe isapp anas update.update-eligible.

The automatic update process does not work as expected, what could be the reasons?

If the flag is not provided by the device (older iOS / macOS version for instance), it may happen that the version from iTunes and the version reported by the device are not accurate (they are filled by hand by the developer and they may be incorrect). Apple introduced the hasUpdateAvailable flag exactly to solve this problem.

From Apple's documentation:

If true, the app has an update available. This key is present only for App Store apps. In macOS, this key is present only for Volume Purchase Program (VPP) apps. This status updates daily and isn’t always up-to-date when installing an app.

Unfortunately, theThe flag provided by the device is not 100%always reliable. FileWave will only requests an app update the application once a day. The InstallApplication command willis not be sent ifagain on the same day when the device reports HasUpdateAvailable=True and the same commandFileWave has been already sent that samecommand. day.If Butthe ifdevice still reports the flag is not properly updated by the device the next day, FileWave will request anthe update.update again.

We have seen reports in the past that someSome iOS versions wouldhave notreported update thethis flag properlyincorrectly even ifafter the application is already up to date. And becauseIf the flag isdoes not updatedupdate within 24h,24 hours, FileWave willmay request the applicationapp toupdate beagain reinstalled everyeach day, which maycan beaffect anusers issue for the end-user or forand network bandwidth. In this situation, the best is to contact FileWave supportSupport and AppleAppleCare Care.so Wethe will help you configuring bothrequired FileWave and your device to gather all the logs Applecan willbe requirecollected. to investigate the issue. Most of the time, upgradingUpdating iOS or macOS to the most recentlatest available version solvesoften resolves the device-side reporting problem.

WhenIn looking at FileWave'sFileWave Client Info for impacted devices, check the Managed Applications tabtab. will show you the value ofIf the flag - if it is always "True", thereafter the app is already current, the issue is likely something wrong on at the device level.or Apple MDM reporting level rather than the FileWave assignment.