BlackBerry UEM Client

for

Android

fixed issues

When trying to activate a device with the

Work space only

(

Android Enterprise

) activation type in a managed

Google

account environment, activation was not successful unless the "Allow additional Google accounts" and "Allow adding and removing accounts" options are enabled. (EMA-18647)

On devices activated with the

Work space only

(

Android Enterprise

) activation type, the

BlackBerry Dynamics Launcher

was briefly visible during the conditional access enrollment even though it was not enabled by the administrator. (EMA-18479)

When the "Validate end-user installed certificates" IT policy rule was assigned, the

UEM Client

also tried to validate certificates from the

BlackBerry UEM

server which were not end-user installed. In some cases, if the server certificates are received and validated out of their intended order, the validation was not successful and therefore the certificates were not installed. (EMA-18374)

During the activation of devices with the

Work and personal - full control

(

Android Enterprise

) or

Work space only

(

Android Enterprise

) activation types, the

UEM Client

was stuck on the Configuring

BlackBerry Dynamics

screen if the administrator enabled the "Start conditional access enrollment after the authenticator broker app is installed" option. (EMA-18477)

When there was a certificate fingerprint mismatch for certificates that the server delivered to the

UEM Client

(for example, trust certificates, root certificates, and SSL certificates), the

UEM Client

did not include sufficient details to determine the cause of the mismatch. The

UEM Client

now logs the details to help determine how and when the mismatch occurred and what caused it. (EMA-18303)

If a device password was out of compliance according to the

BlackBerry UEM

server, the device might not have successfully reported a compliant status to the server if it encountered errors or connectivity issues.  (EMA-18038)

When an App Lock mode profile is assigned to a device, the

UEM Client

was incorrectly displaying extraneous app icons that could not be tapped (for example, the Phone app). (EMA-18016)

When activating a device with the

Work space only

activation type, the activation completed even though there was a personal

Google

account on the device which was not allowed. (EMA-17879)

On a device activated with the

Work space only

(

Android Enterprise

) activation type in a dark site environment, if the VPN profile was assigned prior to device activation, it was not successfully applied to the VPN application. (EMA-17712)

The

BlackBerry Dynamics SDK

has been updated to version 12.1.0.39 to fix an issue where bad OS compliance data from the

BlackBerry UEM

server caused the

UEM Client

to stop responding. (EMA-18398)

There are no fixed issues in this release.

There are no fixed issues in this release.

The

BlackBerry Dynamics SDK

  in the

UEM Client

was updated to version 12.0.1.79, which includes performance fixes.

On

Android

devices that had

BlackBerry Dynamics

configured, if the device was not connected to the network when a Remove Device command was issued, the command failed to remove the Work Profile or to factory reset the

Android

devices. (EMA-17733)

On some devices running

Android

13, a user could not select a specific S/MIME certificate for encryption or signing. (EMA-17652)

The PKI-C Library did not comply with RFC 6211 for CMS algorithm identifier protection validation. (EMA-17636)

The device could not read the LT value (the time value in long format) in the QR code. (EMA-17581)

On devices running

Android

11 and later, when a device was enrolled, the Wi-Fi MAC address was not retrieved and displayed in the Managed Device Users grid (Advanced view). (EMA-17559)

On some

Samsung

devices with the "Specify Workspace Password and Lock" option enabled, after a user changed the work space password, the API did not lock the work space and the user was not required to enter the new work space password. (EMA-17551)

The

UEM Client

used a deprecated API to obtain the device phone number. (EMA-17534)