BlackBerry UEM Client for Android known issues
BlackBerry UEM Client
for Android
known issuesAfter deactivating a Samsung device that was activated with the MDM controls activation type (with the Samsung Knox option enabled), and you try to reactivate it, a "Unknown error: 4025" error message appears if the administrator had assigned a system certificate that's typically pre-installed on the device (such as DigiCert Global Root CA) prior to activation. (EMA-18302) Workaround : In the device Settings > View security certificates menu, enable the system certificates (such as DigiCert Global Root CA). |
When activating a device in a dark site environment with the Work space only ( Android Enterprise ) activation type, if the device uses the Samsung SVPN application, it does not activate successfully. (EMA-17497) |
On some Samsung devices that were activated on Android 12, the IT policy that is assigned to the device is not correctly applied after upgrading to Android 13. (EMA-17465) Workaround : Reactivate the device. |
You might not be able to use Knox Mobile Enrollment to activate Samsung Galaxy A52 or Samsung Galaxy XCover devices running Android 11. (EMA-17342) |
On Samsung devices running Android 11 activated with the Work space only (Android Enterprise ) activation type, Wi-Fi profiles that are configured with a shared certificate are not saved to the device. (EMA-16909) |
On Samsung devices running Android 12, if the "Send usage and diagnostic data" setting is enabled on the device but your administrator assigned a policy rule to disable it, the "Based on the admin policy set for your phone, the following policy has been withdrawn: Sending of Diagnostic Data." warning message appears. (EMA-16746) |
During activation, the user must set a complex password for the work space even though the IT policy is set to numeric or alphanumeric. (EMA-16254) |
When activating a Samsung Knox device, if the screen times out at the Knox license activation screen, the activation is not successful when you try to continue. (EMA-16046) |
On some European models of Samsung devices running Android 11, the device Welcome screen appears during activation when using the Work and personal - full control (Android Enterprise fully managed device with a work profile) activation type. The device is activated correctly and the user can follow device setup screens. (EMA-16014) |
On some Samsung devices that are activated using the Work and personal - full control (Android Enterprise fully managed device with a work profile) activation type, after upgrading to Android 11, the compliance profile incorrectly restricts apps in the personal space. (EMA-15960) |
On Samsung devices activated with the Work and personal - full control (Android Enterprise fully managed device) non-premium activation type, when an administrator unassigns an app, the app isn’t uninstalled but is instead grayed out and cannot be opened. (EMA-14851)Workaround : On the device, manually uninstall the app. |
If the UEM Client is set as the authentication delegate for BlackBerry
Dynamics , and a compliance profile is assigned to users with the "Rooted OS or failed Knox attestation" compliance rule enabled, when the UEM Client is locked due to inactivity and the user enters their password to log in to a BlackBerry
Dynamics app, the password is not accepted. The user is returned to the login screen but the password field is greyed out. (GD-67251) |
On devices running Android 15, the UEM Client app may be reported as a sideloaded app and flagged as a compliance violation even though it was updated from the Google
Play store. (MTDLIB-1974)Workaround : Open the UEM Client app on the device. |
If a device that is configured for Entra ID conditional access is removed from the Entra endpoint portal by an administrator, and the device is unregistered from the Microsoft Authenticator app, the user is not prompted to authenticate when they switch back to the BlackBerry UEM Client app. (UES-9561)Workaround : Force close the UEM Client and reopen it, or tap the icon > Settings > Enroll Conditional Access . Follow the instructions on the screen to authenticate the device. |