Release Notes for Android
Total Page:16
File Type:pdf, Size:1020Kb
BlackBerry UEM Client for Android Release Notes 12.38.2.156999 2021-06-18Z | | 2 Contents What's new in BlackBerry UEM Client for Android............................................. 4 Fixed issues...................................................................................................... 5 Known issues....................................................................................................7 Legal notice...................................................................................................... 9 | | iii What's new in BlackBerry UEM Client for Android What's New in BlackBerry UEM Client for Android 12.38.2.156999 • Bug fixes only. What's New in BlackBerry UEM Client for Android 12.38.1.156983 • Support for updates: Updating from UEM Client version 12.34.x and earlier is no longer supported. You must be running UEM Client version 12.35.x or later to update to the latest version. Devices running an older version must be reactivated. • Device reporting: Changes were made to how the UEM Client reports MEID or IMEI values of devices to UEM. What's new in BlackBerry UEM Client for Android 12.38.0.156961 • New activation method: You can now activate a device using your organization’s identity provider such as Okta or Ping Identity. Administrators must configure this option in the BlackBerry UEM and Enterprise Identity administration console. This feature requires UEM 12.14. • Password change: On Samsung devices, changing your password is now easier when your administrator resets it. • Certificate enrollment: Administrators can now enable a setting in the user credential profiles that allows you to dismiss certificate enrollment and complete it later. • Android support: Devices running Android 7 are no longer supported. | What's new in BlackBerry UEM Client for Android | 4 Fixed issues Fixed issues in BlackBerry UEM Client for Android 12.38.2.156999 On Samsung devices running Android 10 or 11, users could access other apps even though the device was assigned an App Lock mode profile with the Work space only (Android Enterprise) activation type. (EMA-16445) On some devices that were activated with a Samsung Knox workspace, users were prompted to enter the certificate password to install the certificate from the shared certificate profile. (EMA-16419) Fixed issues in BlackBerry UEM Client for Android 12.38.1.156983 On BlackBerry devices powered by Android, the Bluetooth capabilities may have been disabled even though it was allowed by the IT policy. (EMA-16397) When you tried to activate an Android 11 device with the Work space only or Work and personal - full control (Android Enterprise) activation type, but the Work and personal - user privacy activation type was ranked with highest priority, the “Unable to activate device - Unsupported activation type" error message displayed. (EMA-16382) On Android 10 devices, users were not prompted to select a certificate for authentication when trying to access the intranet in a browser. (EMA-16162) After activating an Android 11 device with the Work and personal - full control (Android Enterprise) activation type, you could not install apps from Google Play in the personal space. (EMA-16113) Fixed issues in BlackBerry UEM Client for Android 12.38.0.156961 When you tried to activate Samsung Knox device, sometimes the "Error 102" message displayed and activation was not successful. (EMA-16339) You could not install an app if an administrator set an app config payload with an empty itemListValue. (EMA-16250) On some Android 11 devices, the UEM Client got stuck on the loading screen after trying to unlock the app. (GD-54473) On devices running Android 11, you could not unlock the work space using the facial recognition feature even though the IT policy allowed it. Note that after upgrading to Android 11, you must manually enable facial recognition for the workspace through the device settings. (EMA-16201) On Android 11 devices activated with the Work space only (Android Enterprise) activation type, device logs could not be gathered. (EMA-16120) The status of the "Trust agent inactivity timeout" IT policy setting incorrectly displayed as "Password expiration timeout" on the Assigned IT Policy screen. (EMA-16026) | Fixed issues | 5 On some devices running Android 11, during activation with the Work and personal - user privacy (Android Enterprise) activation type, the device App Info screen of the UEM Client appeared after setting the work space password. (EMA-16021) On BlackBerry devices running Android 8.1, after setting a device password during activation, the UEM Client was minimized. (EMA-16012) When activating a Samsung Knox device with the Work and personal - full control (Android Enterprise) activation type, after setting the work space password and device password, the device password screen persisted in a second app window. (EMA-15930) On Android devices that are activated with the Work space only (Android Enterprise) activation type and assigned an app lock mode profile, the UEM Client and Google Play store did not appear on the home screen. (EMA-14214) | Fixed issues | 6 Known issues Issues that are new in this release are noted with an asterisk (*). * On BlackBerry UEM dark site servers, users cannot activate their devices using the alternate FQDN if it resolves to another FQDN. (EMA-16474) * On Android 11 devices activated with the Work and personal - full control (Android Enterprise) activation type, the user cannot configure Smart Lock settings on the device even though the IT policy rules allow it. (EMA-16454) * If you try to take a screenshot of the UEM Client activation screens (for example, for training purposes), the "Can't take screenshot due to security policy" error message displays even though the device is not activated yet. (EMA-16439) If an administrator changes the password policy rule for the workspace of Samsung Knox devices and the workspace password that was set on a device is no longer compliant, the error message (“Device password does not meet requirements set by the administrator or it’s expired”) displays on the Compliance Report screen in UEM Client. The error message should refer to the “Workspace password” instead. (EMA-16425) When the IT policy rule requires a workspace password and a device password is already set prior to activating a device using the Work and personal - full control (Android Enterprise) activation type, the user is not prompted to set a work space password during activation. (EMA-16279) During activation, the user must set a complex password for the work space even though the IT policy is set to numeric or alphanumeric. (EMA-16254) When trying to activate Samsung Galaxy S20 model devices that are running Android 11, an “Error 3006” message appears and activation is not successful when using the Work and personal - full control (Android Enterprise fully managed device with a work profile) activation type with the ‘When activating Android Enterprise devices, enable premium UEM functionality such as BlackBerry Secure Connect Plus’ and ‘Enable Samsung Knox DualDar Workspace’ options selected in the activation profile. (EMA-16075) When activating a Samsung Knox device, if the screen times out at the Knox license activation screen, the activation is not successful when you try to continue. (EMA-16046) On some European models of Samsung devices running Android 11, the device Welcome screen appears during activation when using the Work and personal - full control (Android Enterprise fully managed device with a work profile) activation type. The device is activated correctly and the user can follow device setup screens. (EMA-16014) On some Samsung devices that are activated using the Work and personal - full control (Android Enterprise fully managed device with a work profile) activation type, after upgrading to Android 11, the compliance profile incorrectly restricts apps in the personal space. (EMA-15960) On Samsung OneUI Core devices that are activated with an Android Enterprise activation type and the premium option enabled, the device may not work correctly when it calls any Samsung Knox APIs because it is not a Samsung Knox device. For a list of Samsung Knox devices, visit the Samsung website. (EMA-15736) | Known issues | 7 On devices running Android 11 that are activated with Work space only and Work and personal - full control (Android Enterprise) activation types, the "Set time automatically" and "Obtain time zone from network" IT policy rules are not enforced. (EMA-15649) On Samsung devices activated with the Work and personal - full control (Android Enterprise fully managed device) non-premium activation type, when an administrator unassigns an app, the app isn’t uninstalled but is instead grayed out and cannot be opened. (EMA-14851) Workaround: On the device, manually uninstall the app. On Samsung Knox devices that are activated with the Work space only (Android Enterprise fully managed device) activation type, the device does not establish a BlackBerry Secure Connect Plus connection if the administrator disables the “Allow user-configured VPN in workspace” IT policy rule. For more information about this issue, visit support.blackberry.com/community to read article 58735. (BSCP-789) When activating a Samsung device running Android 8 with the Work space only or Work space only (Premium) activation types, the facial recognition feature on the device is not available. (EMA-9819) On Samsung Knox 3.0+ devices activated with the Work space only (Samsung Knox) activation type, when the “Disable work space” command is sent to the device, the user sees the password entry screen when trying to access the workspace instead of a locked screen. Later, when the “Enable work space” command is sent to the device, the keyboard does not appear correctly when the user tries to enter the password. (EMA-9809) Workaround: If the keyboard doesn’t appear correctly, press the Power button twice. For Samsung Knox 3.0+ devices activated with the Work space only (Samsung Knox) activation type, when the "Reset workspace password" command is sent to the device, the password reset screen does not display if the device is locked. The user can not access their work space until they set a new password.