A blog with focus on Windows 10 and cloud <solutions
RSS icon Email icon Home icon

  • Version mismatch in custom iOS app causes reporting back to be unsuccessful in ConfigMgr and Intune

    Posted on October 14th, 2014 By Andreas Stenhall + No comments

    I’ve encountered quite an interesting issue when deploying a custom iOS (IPA) app using System Center Configuration Manager and Intune. The problem is that the deployment status for the app never reports as “Success” and is hung at “In progress”. As it turns out there is a mismatch in the version info that exist within the IPA file and the plist file that is included when deploying the IPA.

    The CFBundleVersion listed within the IPA in the file info.plist

    <key>CFBundleVersion</key>
    <string>1.2.3</string>

    must match the bundle-version found in the plist file that is used when creating the app deployment in Configuration Manager.

    <key>bundle-version</key>
    <string>1.2.3</string>

    If these values do not match the status will never be reported as successful in the ConfigMgr console. After the September 2014 maintenance window for Intune I also suspect that this version mismatch is causing the app to be re-deployed over and over again, however this has yet to be confirmed.

    Note: You can easily check the content of info.plist within the IPA by renaming the IPA to ZIP and extract its contents. Use a plist viewer of your choice (there are several free for trial) to check the CFBundleVersion.