BlackBerry UEM Client for Android fixed issues
Fixed issues in the BlackBerry UEM Client for Android 12.55.1.158598
|
After upgrading to the BlackBerry UEM Client version 12.55.0.158589, when a user tried to import an Entrust certificate, the import failed. (EMA-19783) |
Fixed issues in the BlackBerry UEM Client for Android 12.55.0.158589
|
If the text on the license agreement screen wrapped to more than one line (for example, due to a large font size or a narrow portrait display), tapping the check box might not have selected it. (EMA-19682) |
|
If an Android device was paired with a Bluetooth device with a name that contained a double-quote ("), when you viewed the device details in the management console, the screen did not load as expected. (EMA-19654) |
Fixed issues in the BlackBerry UEM Client for Android 12.54.2.158569
|
The UEM Client did not complete SCEP enrollment as expected when the Certificate Management System used RFC 6211 CMS Algorithm Protection with SHA-256 and rsaEncryption. (EMA-19709) |
|
After assigning a user credential profile configured for Entrust smart credentials, when the user tried to activate their smart credential by scanning the Entrust IdentityGuard QR code from the UEM Client, the activation process failed. Users who had previously activated their smart credential were also unable to encrypt email messages. (GD-69763) |
Fixed issues in the BlackBerry UEM Client for Android 12.54.1.158560
|
If you tried to import Entrust certificates into the UEM Client, the import process failed. (GD-69791) |
Fixed issues in the BlackBerry UEM Client for Android 12.46.2.158471
|
Microsoft plans to roll out Baseline Scope Enforcement for conditional access policies starting in May 2026. This release of the UEM Client includes a fix that allows for successful conditional access enrollment when Baseline Scope Enforcement is enabled. (EMA-19599) |