Known issues

For known issues found in previous releases, see the "Known issues" sections in the release notes for those releases, available in MobileIron Core Product Documentation.

This release includes the following known issues:

  • VSP-64029: A Wi-Fi configuration cannot be saved or edited if it contains a proxy variable password setting.

  • VSP-63883: If a device in Device Admin mode is assigned an Android Enterprise configuration with the Android Open Source Project (AOSP) flag enabled, the configuration remains in "Pending" state.

  • VSP-63848: Administrators deploying devices in Airgapped/Android Open Source Project (AOSP) mode as a Shared Kiosk cannot initiate the admin device action to sign out of the Kiosk, due to the dependency of this capability on Google accounts.

  • VSP-63746: Mobileiron Core deployments in Hybrid mode (both Android Open Source Project (AOSP) and Android Enterprise) will not see the AOSP badge displayed for in-house apps.

  • VSP-63713: The Android application package (.APK) file for the Google Chrome app cannot be uploaded as an in-house app and generates the following error message: "App 'com.android.chrome_xxxxxxxxx.apk' import failed: Error while handling file resources."

  • VSP-63628: There is an issue with Microsoft Azure generating incorrect error messages during tenant onboarding when the property "Allow only TSL / SSL connection certified by trusted CA's" is enabled.

    Workaround: To avoid this error, add root certificates for all outbound request URLs to the Trusted Root Certificate page in MobileIron Core.

  • VSP-63413: There is an issue when Core Administration pages are opened in a Chrome browser, on a Windows device with Integration Touch enabled. If you click the last entry of the Safari Domains list, you will be returned to the top of the page.

  • VSP-63303: Core checks for iOS operating system updates every 12 hours in all iOS devices. Expected behavior is that only supervised iOS devices should be making this check.

  • VSP-58532: The Terms of Service (ToS) page does not display during client registrations if the device has been previously registered, deleted, and then re-registered.