Resolved issues

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

  • IOS-18416: Previously, the application name was not updated in the Apple App Store to reflect the new name "Ivanti [email protected]" This issue has been fixed.

  • IOS-18097: For DT Client, "Imprint" was not localized in Italian, Chinese, or Spanish. This issue has been fixed.

  • IOS-17870: Previously, Ivanti [email protected] displayed a threat error after deleting the client and re-registering with Ivanti EPMM. This issue has been fixed.

  • IOS-17771: Upon upgrade, the [email protected] tab now displays as expected.
  • IOS-17656: Featured Banner is now supported in Native App Catalog.

  • IOS-17823: Previously, if an AppConnect app was launched, it resulted in [email protected] displaying the app with an incorrect AppConnect version and a "Pending" configuration status. This issue has been fixed.

  • IOS-17497: Upon launching on iOS 6 beta, [email protected] crashes. This issue has been fixed.

  • IOS-17439: Fixed the issue when the launch of [email protected] client caused delays with connection to captive Wi-Fi networks.

  • IOS-17295: When anti-phishing was enabled, iOS devices sometimes lost network connectivity. This issue has been fixed.

  • IOS-17294: In app registration fix against Connected Cloud Instance.

  • IOS-17201: Fixed an issue when the Secure Apps section in the application Settings was hidden when "Access your Microsoft 365 apps" registration prompt was displayed.

  • IOS-17200: The Azure Active Directory setup screen was not shown if the device was not in compliance. This issue has been fixed.
  • IOS-17093: With the AppConnect policy set to allow biometric unlock (fallback to AppConnect passcode), the device unlock command from the server resulted in [email protected] losing the AppConnect passcode. This issue has been fixed.
  • IOS-17160: The Threat Detection screen displayed after registration in Microsoft 365 Access even though it was enabled in the Core. This issue has been fixed.
  • IOS-17072: When the device was out of compliance, the reason for the Compliance Violation was missing from the Server Info section in the [email protected] application. This issue has been fixed.

  • IOS-17004: After successful Azure Active Directory registration, [email protected] app immediately checks-in with Core for device compliance reporting.

    IOS-16888: Previously, when the AppConnect passcode was not set up, the device user was prompted by AppConnect to create one. Once the passcode was created, the device set up was not completing. This issue has been fixed.