Known issues
This section describes the known issues found in the MobileIron Cloud 75.
For known issues found in previous releases, see the "Known issues" sections in the release notes for those releases, available in MobileIron Cloud Product Documentation.
-
AW-54253: The device search API, /api/v1/device, and user search API, /api/v1/device, with the UID filter performs a case sensitive match on the UID, which may yield unexpected results.
For example, given a user UID of [email protected]:
-
/api/v1/device?q=&dmPartitionId=29807&[email protected]
yields no results. -
/api/v1/device?q=&dmPartitionId=29807&[email protected]
yields one device.
Workaround: Use the email address filter because the email address match is already case insensitive.
-
-
AW-54189: MobileIron Cloud adds duplicate records to the devices report for devices whose device details show records with both the Allow and Block states on the Sentry tab.
-
AW-54116: MobileIron Cloud fails to update the associated Volume Purchase Plan (VPP) license during a VPP sync if the sync involves updating the license type from DEVICE to USER.
-
AW-54115: MobileIron Cloud fails to update the status of disassociated Volume Purchase Plan (VPP) licenses during a VPP sync.
-
AW-54077: The Dashboard -> Apps -> In-House apps charts incorrectly represent updated side-loaded in-house apps as public apps. The In-House apps pie chart also reflects a count mismatch between the number of devices reflected on the pie chart label and the number of devices encountered after drilling down to view the slice.
-
AW-53995: MobileIron Cloud fails to create users with display names longer than 128 characters, which causes LDAP and Azure Active Directory sync errors for any such users.
-
AW-53989: Users cannot log in after reboot to the MobileIron Cloud Connector installed from an Amazon Machine Image (AMI). Logging in after reboot works as expected with ISO 35.
-
AW-53926: Sorting of users is not working as expected in dynamically managed user group details.
-
AW-53874: Some users cannot install Android apps on their devices after they register on MobileIron Cloud an Android Enterprise device, unregister that Android Enterprise device, and then re-register the Android Enterprise device using the same account.
-
AW-53853: The event "LDAP Sync User account(s) updated" on Dashboard -> Notifications presents a clear notification icon when there is no need for the icon because MobileIron Cloud has already cleared the notification internally, but fails to update the user interface accordingly.
-
AW-53852: The count of unmanaged iOS apps that appears in the MobileIron Cloud Apps dashboard only captures the number of apps of app type UNMANAGED, but should also include in the total count the number of apps of app type NOT_APPLICABLE.
-
AW-53832: MobileIron Cloud cannot successfully save the Android APN Settings configuration when an administrator creates it from a German language browser.
-
AW-53818: MobileIron Cloud displays the Notifications menu heading in English in the new look user interface, despite the browser language being other than English.
-
AW-53817: The Update Account API (PUT /api/v1/account) resets some of the user info when the call lacks values for mandatory parameters.
-
AW-53665: MobileIron Cloud reports, and the MobileIron Cloud devices page, display the model identifier instead of the pretty model identifier for MacBook devices.
-
AW-53651: For Windows devices, MobileIron Cloud does not report device compliance status as "Yes" to Microsoft Azure when the device is compliant after registration, causing Microsoft Azure to display "N/A" for device compliance status.
-
AW-53610: Microsoft store searches are currently unavailable in MobileIron Cloud due to API changes or downtime from Microsoft.
-
AW-53585: The App Configurations tabs on the Docs@Work and Web@Work app details pages do display the “AppConnect Custom Configuration” tables.
-
AW-53563: The following advanced device search attributes for advanced search option, "AZURE_DEVICE_COMPLIANCE_STATUS," attribute do not work correctly:
-
AZURE_DEVICE_COMPLIANCE_STATUS EQ 'notCompliant'
-
AZURE_DEVICE_COMPLIANCE_STATUS CONTAINS 'not'
-
AZURE_DEVICE_COMPLIANCE_STATUS CONTAINS 'notCompliant'
-
AZURE_DEVICE_COMPLIANCE_STATUS STARTS_WITH 'notCompliant'
The following attribute works as designed:
AZURE_DEVICE_COMPLIANCE_STATUS NEQ 'notCompliant'
-
-
AW-53385: Audit trails is not capturing all of the Azure Active Directory (AAD) activity description.
-
AW-53343: When a device is enabled for Azure Active Directory (AAD) compliance status reporting in MobileIron Cloud, and the device has not registered with AAD, device is in "interaction required" state. This indicates that client still needs to register with AAD. But the server displays Azure client status as "N/A" instead of "interaction required." Once the device registers with AAD and reports the compliance status to server, the status changes to "success."
-
AW-53338: There are some cosmetic issues on iPod devices related to button colors, animations, and element positioning that manifest during iReg registration of iPod devices.
-
AW-53291: MobileIron Cloud does not apply the Advanced Search filter in the "Users" tab when the administrator navigates from the "User Groups" tab by clicking the user count link of any user group.
-
AW-53169: MobileIron Cloud's Windows Store search does not return applications that only run on HoloLens devices when the search criteria is the name of a HoloLens-only application name.
-
AW-53026: There are some text overlap, button color, and element positioning issues on some iOS devices during the Terms of Service stage of registration.
-
AW-52901: The MobileIron Tunnel configuration for iOS and macOS works only with TCP_ANY option. IP_ANY is not supported. If the administrator selects IP_ANY and saves the iOS or macOS configuration, the configuration defaults to the MobileIron Windows or Android configuration.
-
AW-52845: The MobileIron Cloud audit trails feature does not capture script association changes for MIP archive apps.
-
AW-51354: Changing and attempting to save any value on the Account Info page invokes a "Page not found" error message.