Fixed issues in BlackBerry UEM Cloud

On 

OnePlus

 and Redmi devices, in certain circumstances, 

BlackBerry Dynamics

 apps could get stuck in an authentication loop. (FIRST-17108)

If you configured a list of approved device IDs for 

Android

 devices, and selected the 'Allow only approved device IDs' option in your activation profile, if you activated an 

Android

 device that was not in the approved list, the activation did not fail. (EMM-136003) 

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)

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 was created. (EMM-137108)

iOS

 device users were not able to access apps and sites without using their credentials after an administrator had assigned a SCEP profile and a single-sign on profile to them. (EMM-137085) 

The compliance violations list in the management console were empty for apps that were built using newer SDKs. (GD-47035)

In an environment that used 

BlackBerry Secure Connect Plus

 with 

Samsung Knox

 devices, if the environment blocked the *.secb2b.com call from 

BlackBerry UEM

, the 

Knox

 (KLM/ELM) license might have expired. (EMM-140039)