BlackBerry UEM Client

for

Android

fixed issues

If a user's

Samsung

device had an app lock mode profile assigned and was limited to more than one app, when the user was on the

BlackBerry Dynamics

password screen, they could not use the

Samsung

home button to exit the screen. (EMA-19285)

If the

UEM Client

was set as the authentication delegate for

BlackBerry Dynamics

, and a compliance profile was assigned to users with the "Rooted OS or failed Knox attestation" compliance rule enabled, when the

UEM Client

was locked due to inactivity and the user entered their password to log in to a

BlackBerry Dynamics

app, the password was not accepted. The user was returned to the login screen but the password field was greyed out. (GD-67251)

The

BlackBerry Protect Mobile

insecure

Wi-Fi

detection feature might not have worked as expected on devices with

Android OS

16. (MTDLIB-2018)

When users tried to activate

Pixel

10 XL devices, the activaton process did not complete as expected if you enabled the "Rooted OS or failed Knox attestation" setting in the assigned compliance profile. (EMA-19273)

If a user tried to activate a

Samsung

S25 device with a SIM card using an

Android Enterprise

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

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)