Fixed issues in BlackBerry UEM 12.12 MR1
User and device management fixed issues
On OnePlus and Redmi devices, in certain circumstances, BlackBerry
Dynamics apps could get stuck in an authentication loop. (FIRST-17108) |
Management console fixed issues
If an administrator restricted versions of a BlackBerry
Dynamics app using the BlackBerry UEM management console, the way the restricted version number was processed may have unintentionally blocked more versions of the app than intended. (FIRST-17124) |
If you were using an LDAP connection to an Active Directory environment and you made a change to a user's attributes such as the email address, the change would not synchronize with UEM. (EMM-136693) |
BlackBerry
Dynamics -hosted .apk files were not installed on devices if the activation profile was enabled for Google
Play . (EMM-137637) |
When you edited an app configuration for a hosted app, a duplicate app configuration might have been created. (EMM-137108) |
iOS device users were not able to access apps and sites without using their credentials after an administrator assigned a SCEP profile and a single-sign on profile to them. (EMM-137085) |
The compliance violations list in the management console might have been empty for apps that were built using newer SDKs. (GD-47035) |
BlackBerry Secure Connect Plus fixed issues
BlackBerry Secure Connect Plus
fixed issuesIn an environment that used BlackBerry Secure Connect Plus with Samsung Knox devices, if the environment blocked the *.secb2b.com call from UEM, the KNOX (KLM/ELM) license might have expired. (EMM-140039) |