Limitations

These are cumulative release notes. If a release does not appear in this section, then there were no associated limitations.

  • IOS-18346: Due to Apple's design limitations, Ivanti [email protected] may be shortened to three dots at the end and have spaces removed on certain devices.

    Workaround: None

  • IOS-18228: After upgrading the Ivanti [email protected] client, the Mobileiron logo/icons may continue to display due to caching.

    Workaround: To refresh the screen/cache, simply swipe the screen after the Ivanti [email protected] client upgrade and the cache may be cleared.

  • IOS-18097: For DT Client, "Imprint" is not localized in Italian, Chinese, or Spanish.

    Workaround: None.

  • IOS-17703: GCC and DoD Tenant types are not supported for Azure Device Compliance feature by branded clients.

    Workaround: None.

  • IOS-17628: During enrollment, Lockdown should be tuned off while installing the MDM profile. Once the device has been successfully enrolled and the MDM profile was successfully installed, the device user can enable Lockdown again.

  • APG-1208: For iOS 15 devices, unable to install [email protected] on the device after signing the app.

    Workaround: Applications that were signed on macOS 10.15 "Catalina") or older should be re-signed using macOS 11.x ("Big Sur") or newer. For more information, see article: iOS 15: In-House / Enterprise Apps Fail to Install.

  • IOS-17330: When anti-phishing is enabled, VPN sometimes turns off while browsing on a cellular network. This could cause issues while browsing and downloading apps.

  • IOS-17329: When anti-phishing is enabled on the device, App download and page loading sometimes fails.

    Workaround: Turn off and then turn on the VPN to fix the issue.

  • IOS-16982: On an iOS device with Azure Active Directory device compliance configuration, Microsoft shows Page not found error instead of non-compliance message when the device is out of compliance.

  • IOS-16100: Device is not getting removed from the Microsoft Azure portal when device is de-registered from the Microsoft Authenticator portal. As a result, Microsoft 365 Access status is not getting updated on the device. There is no workaround for this issue.