BlackBerry UEM Client

for

Android

fixed issues

If you enabled

Knox

DualDAR encryption and selected the encryption app in the assigned activation profile, when a

Samsung

device user tried to activate using the

Android Enterprise

Work and personal - full control

activation type, the activation did not complete as expected. (EMA-19100)

The activation process did not complete as expected on

Android

13 devices without SIM support. (EMA-19088)

As of

UEM Client

version 12.45.0.158273, if a user was assigned an Intercede user credential profile and an enterprise connectivity profile with "Container wide VPN" enabled, by default the

UEM Client

routed container wide VPN traffic through

BlackBerry Secure Connect Plus

to

UEM

. On

Pixel

devices, if you assigned the Intercede user credential profile to the user after they activated with an

Android Enterprise

activation type, the user's device continued to route VPN traffic directly to

UEM

instead of routing it through

BlackBerry Secure Connect Plus

. (EMA-19060)

If you configured

Entra ID

conditional access, on devices with the OS language set to French, the

Microsoft

Online device registration screen was not translated into French. (EMA-18988)

As a result of

Google

’s deprecation of

SafetyNet

attestation, the activation process for

BlackBerry Dynamics

apps was taking up to 5 minutes to complete. (GD-67446)

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)