Resolved issues

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.

AC-22173: When the locale is set to French, the Mobile@Work client crashes approximately 15 minutes after check-in with the server. This issue is now fixed.

AC-22099: Provisioning of Realwear device T21G in Managed Device (Device Owner) mode failed with error message "Cant setup device". This issue is now fixed.

AC-22081: When Android 12+ devices in Managed Profile (PO) mode have a Wi-Fi configuration that uses identity certificate and location permission is not being granted by the device user during client provisioning, an attempt to start certificates re-provisioning through the client's Settings caused Mobile@Work client to crash. This issue is now fixed.

AC-22078: On Android 7 devices, the provisioning of Managed Profile (aka Profile Owner) mode could not be completed when the call log was requested and the "Require device identifiers for enrollment" option was set in Ivanti EPMM. Mobile@Work kept asking the device user for Phone Permission Granting - but phone permission appeared granted and locked. This issue is now fixed.

AC-22041: Previously, when you registered a device, imported a public app to the device, then set Apple Play Store to Apps@Work, the public app status displayed as free, even though the status changed to installed when you clicked on the app. This issue has been fixed.

AC-21784: Previously, on Samsung devices with OS v7, the Threat card in MTD was taking too long to display and the back button was not returning device user to the Mobile@Work Home page. Additionally, the Phishing scan worked intermittently. These issues have been fixed.

AC-21777: Device user was asked to grant phone permission after migration to Managed Profile mode, even after phone permission was granted before migration. This issue is now fixed.

AC-21841: Installation of certificates on Android 11+ devices sometimes failed during enrollment to Managed Device mode and recovered after client restart or device reboot. This issue has been fixed.

AC-21827: On Samsung devices with Android 12 and Mobile@Work for Android 11.7.0.0 enrolled via KME, a message displayed: "Warning banner cannot be enabled without premium Knox license" even though that option in the Privacy Policy was not activated. This issue has been fixed.

AC-21814: For non-enterprise modes, the MTD disable-Bluetooth local action was not supported on Android 13. If a threat was detected and this action was specified, a threat action notification was incorrectly displayed. This issue has been fixed.

AC-21732: Department of Defense warning banner was not displaying after Android devices rebooted. This issue has been fixed.

AC-21623: Corrected Deutsch punctuation usage in Mobile@Work client > device registration.

AC-21565: When firewall was misconfigured in a way that allowed initial communication with Ivanti EPMM during device registration while, at the same time, blocking next communications via different check-in URL, Mobile@Work crashed. This issue is now fixed; Mobile@Work displays the proper error message instead of crashing.

AC-21701: Unable to enroll Mobile@Work Android devices due to Microsoft Authenticator throwing an "error in configuration" when trying to register in Microsoft Azure. This issue has been fixed.

AC-21605: During authentication, Mobile@Work was unable to complete enrollment in Device Owner mode and Work Profile in Company Owned Devices mode. This was due to the inability to perform the check-in because of some race conditions. This issue has been fixed.

AC-21502: When the Zebra OTA upgrade was successfully completed, the installation file was not removed from the temp folder. This issue has been fixed.

AC-21447: On Android 12 devices in Profile Owner (PO) mode, Mobile@Work cannot report the password type (quality) and password length in Ivanti EPMM. This issue has been fixed.

AC-21446: In new enrollments and factory resets, due to attempting to process large CRL files, Mobile@Work 11.5.0.0 crashes when the device user enters the URL. This issue has been fixed.

AC-21428: Specific devices, Zebra TC51 and TC52, stop responding at startup for ten minutes until the kiosk appears. This issue has been fixed.

AC-21423: On Android 12 devices, Mobile@Work needed to be launched manually by the device user to grant location permission and finish the provisioning of Android Enterprise Work Profile on Company Owned Device mode. This issue has been fixed.

AC-21406: Phone permissions granting was not enforced by Mobile@Work even when set as mandatory by Ivanti EPMM. This issue has been fixed. Device users cannot opt out granted phone permissions. Additionally, phone permissions granting is enforced even after device user revokes permissions.

AC-21447: On Android 12 devices in Profile Owner (PO) mode, Mobile@Work cannot report the password type (quality) and password length in Ivanti EPMM. This issue has been fixed.

AC-21446: In new enrollments and factory resets, Mobile@Work 11.5.0.0 crashes when the device user enters the URL. This issue has been fixed.

AC-21398: Some Samsung devices provisioned in Work Profile on Company Owned Device mode rebooted randomly after the creation of a Google account on the personal side. This occurred after application of the latest security patch update. This issue is now fixed.

AC-21387: The Device side camera state in the Lockdown policy was not reported properly for Work Profile on Company Owned Devices. This issue is now fixed.

AC-21381: On Sharp Aquos Android 10 and Android 11 devices, Mobile@Work was crashing upon launch due to problems with default initialization of WorkManager. This issue is now fixed.

AC-21370: Login to Kiosk was failing intermittently due to a race condition. This issue is now fixed.

AC-21362: Provisioning of some low-end devices in Work Profile on Company Owned Devices mode was failing due to the provisioning mode selection being aborted by Android. This issue is now fixed.

AC-21360: Provisioning of Device Owner mode on Android 11+ devices forced launching of Mobile@Work before the device user accepted the Google Terms of Service. This then caused Google Play Services to be unavailable for installation of the Microsoft Intune Authenticator app, thus blocking device provisioning. This issue is now fixed.

AC-21302: After the device restart, while waiting for server configuration, the Kiosk did not apply lock task mode. Meanwhile, the volume control settings option allowed the device user to enter the Settings screen. This issue is now fixed.

AC-21247: Provisioning of Device Owner mode on Android 11+ devices was not using the correct registration method set up on Ivanti EPMM because the Device Owner mode status was not correctly reported back to Ivanti EPMM during registration. This issue is now fixed.

AC-21241: Previously, when attempting a device OS upgrade to Android 11, device users with legacy Device Admin mode active and Mobile@Work were forced to the device Settings screen to grant READ_PHONE_NUMBERS permission. This permission is a dangerous permission introduced in Android 11 that cannot be automatically granted when a device is not provisioned in Android Enterprise mode. Due to a bug in Mobile@Work, this permission was not explicitly requested, forcing device users to device Settings and resulting in confusion because "phone permissions" displayed as already granted. A workaround is available on some phones: device users can revoke and re-grant phone permission while in this state. However, on other devices, this option was not possible and created an endless loop of permission granting requests. This issue is now fixed.

AC-21226: Attestation was always displayed as "Unknown" in the Ivanti EPMM Device details page. This issue has been fixed.