Fixed issues in

UEM

12.20 and

UEM Cloud

In environments with one instance of

UEM

, when you checked the installed version in

my

Account

, it was incorrectly displayed as one version behind the actual version that was installed. (EMM-157259)

In specific circumstances, when

UEM

synchronized directory groups, it could load a large number of objects into local memory and cause an out of memory event. (EMM-157721)

In specific circumstances, when

UEM

synchronized a large number of directory groups, it could cause an out of memory event. (EMM-157719)

This release includes updates to the Spring Framework for the

BlackBerry Connectivity Node

. (EMM-157499)

During startup, the

BlackBerry UEM Core

did not correctly handle the version string format for certain patch releases of JRE 17. If this occurred, the

UEM Core

did not start as expected. (EMM-157607)

If you configured

Kerberos

Constrained Delegation (KCD) for

BlackBerry Dynamics

apps, the following issue occurred if KCD authentication failed for a user:

For an
Android
user, the prompt for the user’s credentials was delayed.
For an
iOS
user, the user was not prompted for their credentials.

(EMM-157238)

If you configured

UEM

to connect to more than one

Microsoft Active Directory

instance, when you searched for a user account to add from

Active Directory

,

UEM

might not have found the user account as expected because it searched the wrong

Active Directory

instance. (EMM-157231)

In a

UEM Cloud

environment,

BlackBerry Dynamics

apps could not retrieve a user certificate using a SCEP profile configured with a dynamic SCEP challenge password. (EMM-157026)

When

BlackBerry Secure Connect Plus

or

BlackBerry Proxy

made an authorization check for a device, if the checked failed, it would not attempt another authorization check for at least one hour. (EMM-156726, EMM-157016)

Extra logging information has been removed from Debug logging. (EMM-156885)

When you tried to upgrade

UEM

, the process might have timed out during the

UEM

database upgrade. (EMM-156408)

If you tried to add certain

Android

APKs that were published to

Google Play

to

UEM

as internal app, the APK file could not be verified. (EMM-156847)

Additional logging has been added for calls to

Google

APIs for publishing hosted applications. (EMM-156841)

Under specific conditions, when you tried to update a hosted internal app, the update might have failed. (EMM-156828)

The organization logo did not display as expected in the

Org Connect

organization profile. (EMM-156539)

If you navigated to the

Org Connect

section in the management console, a notification message displayed indicating that the

Org Connect

plug-in requires

BBM Enterprise

, but the Next button was greyed out. This prevented you from registering

Org Connect

. If

Org Connect

was registered previously, you could not manage your connection. (EMM-156520)

If you assigned an app group to a user or group, when you edited that user or group you could not change the disposition of the app group. (EMM-154392)

If you activated both

Android Enterprise

and

Android Management

devices, then removed the

Android Management

connection from

UEM

, the console displayed an incorrect count of the devices to be removed. The count included both

Android Enterprise

and

Android Management

devices. Only

Android Management

devices are removed. (EMM-154081)

In a

UEM Cloud

environment, if you turned on "Send SMS/MMS logs to the BlackBerry Connectivity Node" or "Send phone logs to the BlackBerry Connectivity Node" in an IT policy and the

BlackBerry Connectivity Node

was not installed, the following error displayed: "An error was encountered. The profile could not be created." The error message should have indicated that the settings could not be enabled because the

BlackBerry Connectivity Node

was not installed. (EMM-154049)

In the Device tab of an org unit, if you tried to configure a scheduled reboot, you could not save the configuration unless you updated all three sub-fields. (EMM-153890)

When you viewed the device details for a user with more than one SIM, the expand and collapse arrow did not display as expected for SIM 1. You could still expand and collapse the SIM details. (EMM-153727)

Entra ID

directory synchronization reports did not display changes to users' group membership after the report was run. (EMM-153691)

The value of the variable %ComplianceDynamicsEnforcementActionWithDescription% did not display as expected in compliance notification emails that were sent to users. (EMM-151056)