After upgrading to BlackBerry UEM version 12.24, UEM might have sent email profiles and certificate profiles to iOS devices again even though those profiles had not changed. (EMM-162113)

After upgrading to UEM version 12.24, when you tried to use BlackBerry Web Services profile calls, the calls failed with a permissions error. (EMM-161889)

The management console might have indicated that an app was not updated to the latest available version on an iOS device, even though the app was already updated to that version. (EMM-162224)

If UEM sent an app installation request to an Apple device that was pending, and then sent another app installation request to the same device, the latest request was completed but the pending request was delayed until the next time the device checked in with UEM. (EMM-162190)

If you created and assigned a user credential profile that was set up for manual certificate upload, when you later tried to remove a user credential certificate from a user, the request might have timed out. As a result, the certificate was not removed. (EMM-161987)

If a user removed an assigned app with a required disposition from their Apple device, UEM did not install the required app again as expected. (EMM-161666)

If you assigned a Wi-Fi profile that was configured to use an OpenTrust user credential profile to an iOS device, and the device could not receive the profile (for example, because it was locked or busy), UEM requested a new certificate from OpenTrust in each subsequent attempt to send the profile. (EMM-161253)

After you upgraded UEM, if the admin UI service started before the UEM database was running, you might not have been able to log in to the management console. (EMM-159152)

If "Enable BlackBerry Secure Gateway" and "Use OAuth for authentication" were selected on the iOS tab in an email profile, when you edited the profile and cleared these settings, you could not save the changes because the Save button was cut off on the bottom of the screen. (EMM-159512)

After receiving the November 2025 UEM Cloud update, if you tried to create or change a directory synchronization schedule, the management console might have stopped responding when you clicked Add, and the synchronization schedule was not saved. (EMM-159169)

When you viewed a user's details in the management console, an app group that was assigned to the user through nested group membership might not have displayed as expected, even though the apps from that app group were still assigned and available to the user. (EMM-159109)

If you were logged in to the management console using the macOS Safari browser, the Log Out and Help links in the top right of the console were cut off and could not be clicked. (EMM-159083)

If you created a Microsoft Intune app protection profile and tried to add Intune-managed apps from the App package IDs list, the available apps were not displayed. (EMM-159018)

When you navigated to Settings > Migration and followed the steps to migrate users, devices, and configurations from another UEM instance, some UI elements might not have displayed as expected. (EMM-158892)

If a user tried to use UEM Self-Service to set an activation password with exactly 15 characters, and the 15th character was a hexadecimal value (0-9, A-F, a-f), the activation password was not created and the user received a "Failed" error message with no details. (EMM-159157)

If you searched for a Microsoft Active Directory user with a name that contained an apostrophe ('), UEM did not return that user account as expected. (EMM-159146)

If you added a user to UEM and assigned them to a group configured for BlackBerry 2FA as part of the user account creation process, the user might not have received the BlackBerry 2FA configuration, and was not prompted for 2FA authentication when the user logged in to the management console or UEM Self-Service. (EMM-159108)

If you added the "Threema Work For Companies" app to UEM and tried to add an app configuration from a template as part of the process for adding the app, an error message indicated that the XML template could not be updated. (EMM-159032)