Known issues

For known issues found in previous releases, see the "Known issues" sections in the release notes for those releases, available in MobileIron Core Product Documentation.

This release includes the following known issues:

  • VSP-64632: There is an issue whereby macOS devices registered using International Roaming Expert Group (iREG) or Apple Automated Device Enrollment (DEP) cannot subsequently register to Mobile@Work, because the Wi-Fi MAC address is not reported properly to Core. There is no workaround.

    NOTE: Other macOS devices are not affected.

  • VSP-64566: There is an issue where Android Open Source Project (AOSP) devices are unable to set up Email+ because a required identity certificate is not being pushed to Mobile@Work. There is no workaround.

  • VSP-64583: There is an issue where Core 11.1.0.0 can support no more than 10,000 Lightweight Directory Access Protocol (LDAP) group edit requests. There is no workaround. For more information about LDAP groups, see the "Managing Users" chapter of Getting Started with MobileIron Core.

  • VSP-64521: There is an issue with Security Assertion Markup Language (SAML)-enabled devices where, if "Anonymous" is the authentication type selected in their enrollment profile, Core incorrectly registers the device user as "Anonymous."

    Workaround: Select either Password or PIN authentication type to avoid this error.

  • VSP-64471: There is an issue where new Mobile@Work options to enable Zips anti-phishing protection on the personal side of devices are not accessible when added as a Public App and enabled for Android Enterprise.

    Workaround: If Mobile@Work is added as an in-house app, these restrictions are displayed in Android Open Source Project (AOSP) mode.

  • VSP-64390: There is an issue where, when an LDAP configuration is associated with 10,000 or more groups, there may sometimes be a slow response or timeout of the user interface while rendering the list.

  • VSP-64375: There is an issue where Core fails to save Android device details, which could break the Android Enterprise, MTD activation, and other functions which rely on device details. This issue occurs when:

    • An invalid license key is used in the MTD activation configuration

    • A colon ( : ) character is used in the configuration name

    Workaround: Enter a valid license key for MTD, and do not use colons in the configuration file name.

  • VSP-64191: The LDAP Sync function cannot import more than 1000 organizational unit (OU) objects. Thus, some OU objects can be missing on the LDAP user management page.

    Workaround: Assign roles based on LDAP group.

  • VSP-64188: There is an issue where, if there are MobileIron Sentry devices on the network that have attachment control enabled, Core also sends the encryption key in the Docs@Work configuration to Sentry devices that do not have attachment control enabled.

  • VSP-64123: There is an issue where bulk enrollment of iOS devices fails after the Core to Cloud migration service upgrade.

  • VSP-63798: There is an issue in the Core App Catalog, in which only the primary "version" value of an app displays, and the "alt_version" value does not. This can occasionally cause the App Catalog page to list what looks like the same app twice, even though their alt_version values differ.