Resolved issues

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

  • 1491576: Ivanti Mobile@Work mode or Lock Task apps could launch after rotating the device a couple of times; this issue is now fixed.

  • 1266857: Previously, the Android Enterprise managed applications were hidden on Android 14 devices after a first device reboot. This issue is now fixed.

  • AC-22807: Previously, a device in EPO mode was wiped when the server sent retire commands on EPMM. This issue is now fixed.

  • AC-22669: Previously, during registration of a new Android device in Device Owner mode, the applications were missing in Managed configurations. This issue is now fixed.

  • AC-22527: Previously, compliance actions were still in effect even when device threat was mitigated. This is has been fixed for the upgrade scenario.

  • AC-22501: Previously, device-managed applications configuration were enabled before the DO provisioning on Android 11 and later devices were obtained. This issue has been fixed by checking current status to ensure that enable managed app configs is done only if the client obtained any AE privileges (PO, EPO, DO) .

  • AC-22491: Previously, the status of lockdown control "Allow Data Roaming" was not reported correctly on Android 10+ devices provisioned in Managed Device mode. This issue has been fixed.

    Status of lockdown control "Tethering - Bluetooth" in Samsung sub-section of Managed device section in Lockdown policy for Samsung devices provisioned in Managed Device mode was not reported correctly.
    This issue has been fixed and the status is reported as "Not supported".

  • AC-22407-Previously, the Mobile@Work application background in the notifications was not consistent across devices. This issue is now fixed.

  • AC-22525: Previously, the compliance action was not mitigating in device after removing it from the security policy in core. This issue has been fixed.

  • AC-22470: Previously, Wi-Fi was disconnecting and intermittently available on Mobile@Work 11.11.0.0.
    This issue has been fixed.

  • AC-22411: Previously, configuring domain names were not supported in the Wifi configuration for TLS and TTLS authentication protocols. This issue has been fixed.

  • AC-22407: Previously, the Mobile@Work application background in the notifications was not consistent across devices. This issue has been fixed.

  • AC-22368: Provisioning of some slow Android 11+ devices (like Samsung Xcover) randomly became stuck during enrollment. This issue has been fixed.

  • AC-22343: Mobile@Work device users saw the notification "Configuration required" when Mobile@Work ran in the foreground. This issue has been fixed. The notification will now display only when Mobile@Work stays in the background.

  • AC-22344: Previously, Mobile@Work 11.10.0.0 crashed when customers migrated devices from Ivanti EPMM to Ivanti Neurons for MDM with Lookout configuration present on Ivanti Neurons for MDM.
    Now, customers must upgrade to Mobile@Work 11.11.0.0 on which Lookout is supported and then migrate to Ivanti Neurons for MDM.

  • AC-22320: On a dual-SIM Android device, when the second SIM slot is used, the IMEI and IMEI2 values are reported as the same. This issue has been fixed

  • AC-22294: When an iOS device was being unlocked from the My Devices tab on an Android device, an unwanted UI screen was displaying. This issue has been fixed.

  • AC-22201: In Ivanti EPMM, when the Retire compliance action was added as a security policy constraint, it retired the Android devices in Work Profile mode and Work Profile on Company Owned Device mode. However, the devices still displayed as active and even though the devices were retired, the out-of-compliance device count did not change. This issue has been fixed.

  • AC-22097: Previously, the closed loop value corresponding to the Tunnel installation warning was not updating with Ivanti EPMM because the client re-branding was not done in that release. As a result, the "MobileIron" reference in the warning text was still displaying. This issue has been fixed.

  • AC-22341: After the migration from Ivanti EPMM to Ivanti Neurons for MDM, when the Android devices were connected to a managed TLS Wi-Fi network, devices were losing the Wi-Fi connection after the client upgraded from Ivanti Go version 89 to 90. This issue has been fixed.

  • AC-22300: Phone display size incorrectly reported to Ivanti EPMM > Device Details. This issue has been fixed.

  • AC-22292: Intermittently long (160+ characters) SMSes were received with some fragments missing. It happened due to a fix that checked SMS's timestamps and was supposed to filter out SMSes that were received twice on some devices. In the case of long fragmented SMSs, some of its fragments transmitted back to back might have the same timestamps (measured in milliseconds) and thus were filtered out due to this logic. This issue is now fixed.

  • AC-22288: Enrollment type Knox Mobile Enrollment or Zero Touch Enrollment was not properly saved/restored if the device was rotated during registration. This issue is now fixed.

  • AC-22260: In Kiosk AppSetting > Kiosk Branding on Ivanti EPMM, the status bar was not visible in Kiosk mode when the Banner background color was set to black (#050404.) This issue is now fixed.