Skip Navigation

BlackBerry UEM Client
for
iOS
fixed issues

Fixed issues in the
BlackBerry UEM Client
for
iOS
12.52.3702

When a user viewed assigned IT policies in the
UEM Client
, IT policy names longer than 10 characters were truncated and displayed with an ellipsis. The full IT policy name is now displayed. (EMA-18854)
In rare circumstances, when a user opened the
UEM Client
it would stop responding and close. (EMA-18837)
If you configured devices to obtain derived credentials from Intercede MyID, after the user started the activation process they may have received the prompt for Intercede integration before the activation was complete. (EMA-18800)
When a user entered the server address during the activation process, auto-correct could change the server address. Auto-correct is now disabled on the server address field. (EMA-18770)
If you configured devices to obtain derived credentials from Intercede MyID, on
iPad
devices users did not receive a prompt to start the process to import certificates from MyID. (EMA-18761)
If you configured devices to obtain derived credentials from Intercede MyID, for
Apple
DEP devices that were already activated, derived certificates might not have been imported as expected into the native keystore. (EMA-18759)
If a compliance profile is assigned to a device with jailbreak detection enabled, when a device was jailbroken it had a correct compliance status in the
UEM
management console, but this was not reflected in the compliance status in the
UEM Client
. (EMA-18722)
A user could still receive prompts to enable location services even if location services were disabled. (EMA-18715)
Location services could be enabled for the
UEM Client
even though the device did not receive a profile that required location services to be enabled. (EMA-18713)

Fixed issues in the
BlackBerry UEM Client
for
iOS
12.51.3667

There are no fixed issues in this release.

Fixed issues in the
BlackBerry UEM Client
for
iOS
12.51.3643

After activating an
Apple
DEP device, the user was not prompted to enable remote notifications until they minimized and reopened the
UEM Client
. (EMA-18723)
When the UEM Client was open on devices that didn’t have BlackBerry Dynamics enabled, the device’s idle timer was disabled, which prevented the device from automatically locking when the app was open. (EMA-18514)
On devices activated with the
User privacy
activation type, if the administrator configured insecure
Wi-Fi
access point detection and set compliance actions, the device was considered to be out of compliance when the user was not properly prompted to grant location access permission or if they declined it. The
UEM Client
did not indicate that location access was required to resolve the insecure
Wi-Fi
compliance violation. (EMA-18496, EMA-18497)

Fixed issues in the
BlackBerry UEM Client
for
iOS
12.50.3520

On shared devices, the "Check-in" and "Check-out" buttons were not translated when the device language was set to German. (EMA-18348)
After upgrading to
UEM Client
version 12.49.3377, when the user tapped the "Authenticate now" button on the Direct Authentication screen, a spinning circle appeared for an indefinite amount of time as if there was a delay but the feature had already successfully activated. (EMA-18195)
On the IT Policies screen, the "Name of the device IT policy instance" did not appear at the top of the list. (EMA-17976)
The language of disclaimer text and end-user license agreement checkbox did not match the device language. (EMA-17960)
Apple
DEP devices that were assigned a
BlackBerry 2FA
profile with one-time password turned on before activation could not generate a one-time password after activation. (EMA-17755)

Fixed issues in the
BlackBerry UEM Client
for
iOS
12.50.3481

There are no fixed issues for this release.