CylancePROTECT Mobile

fixed issues

If a user deactivated the

CylancePROTECT Mobile

app, then changed the device language and activated the app again, the text on the activation screen used the original device language instead of the new device language. (UESAPP-3111)

If you added an app to the

CylancePROTECT Mobile

restricted list in the management console, when the app was detected on devices, the user might have received more than one new threat notification. (MTDLIB-1176)

If the Network protection >

Wi-Fi

security feature was turned off in the app and the user turned it on and selected "Maybe Later" in the permission prompt, the app indicated that a threat was detected. (MTDPLR-19)

When you navigated to a user's device details in the management console and viewed Alerts > Protect Mobile Alerts, if you tried to filter the results to

SafetyNet

or

Play Integrity

attesation failure alerts, the results were not filtered and the following error message displayed: "An error occurred. Please try again." (UES-13110)

Some status messages, tooltips, labels, and descriptions in the management console referenced

SafetyNet

attestation when they should have referenced

SafetyNet

and

Play Integrity

attestation. (UES-13010, MTD-7931, MTD-7927)

If the

CylancePROTECT Mobile

app was installed and activated in the

Intune

portal on an

Android OS

13 device, in the App info, the "Pause app activity if unused" option was greyed out and the user could not turn it off. This prevented the user from turning off battery optimization for the app, and they saw a warning message in the Device Health section that they could not dismiss. (UES-10189)

App configurations that you created from the

Cylance

console did not register successfully for

Android

devices with the

CylancePROTECT Mobile

app version 2.2.0.1381. This issue was fixed by a

Cylance Endpoint Security

update on March 24 2022. (UES-7516)

For

CylancePROTECT Mobile

devices configured for Intune integration, if the user did not complete

Microsoft

Online Device Registration, when the user force closed and reopened the

CylancePROTECT Mobile

app, the

Microsoft

Online Device Registration banner with the register link did not display as expected. (UES-7243)

When

Play Integrity

or

SafetyNet

attestation failed, the user received a notification on their device even if the

CylancePROTECT Mobile

policy was not configured to display device notifications for attestation issues. (UESAPP-3962)

In the

CylancePROTECT Mobile

app, if some device security features were turned off and no device security threats were detected on the device, the text in the Device Health > Device security section of the app displayed in yellow instead of green. (UESAPP-3644)

After a user turned on

Wi-Fi

protection in the

CylancePROTECT Mobile

app and granted the required permission, a false “No Wi-Fi connected” threat displayed for a few seconds. (UESAPP-3269)

After a user activated the

CylancePROTECT Mobile

app, when the user tapped Device Health for the first time, there could be a delay of up to 20 seconds before the UI displayed. (UESAPP-3154)

After a user activated the

CylancePROTECT Mobile

app and granted permissions for the app to check the security of the

Wi-Fi

network, for up to 30 seconds, Device Health > Network Protection indicated that network security features were disabled. (UESAPP-3147)

If a user tried to activate the

CylancePROTECT Mobile

app on a

Samsung

S20 or S21 device with

Android

12 using their activation credentials, the activation failed with the following error: "The specified key does not exist." (UESAPP-2865)

If you removed an app from the

CylancePROTECT Mobile

safe list or unsafe list, it could take up to 30 minutes for that change to take effect on devices (for example, if an app was removed from the safe list and was considered malicious by the

CylancePROTECT

cloud services, it could take up to 30 minutes for the

CylancePROTECT Mobile

app to detect it). If malware detection was turned off on in a

CylancePROTECT Mobile

policy and you turned it on, it could take up to 30 minutes for the

CylancePROTECT Mobile

app to start detecting malicious apps. (UESAPP-2547)

If a device was activated on

BlackBerry UEM

with the

Android Enterprise

activation type using

BlackBerry Secure Connect Plus

, when the

CylancePROTECT Mobile

app was installed in the work space as a required app, a network connection error occurred when the user tried to activate the app. The app did not activate successfully. (UESAPP-2251)

If a user's device was rooted, when the user moved the

CylancePROTECT Mobile

app from the background to the foreground, a "Threat detected" notification might have displayed on the device. (UESAPP-2210)

If you turned on Unsupported OS in a

CylancePROTECT Mobile

policy and added OS 16.4.1.(a) to the unsupported list, when the policy was applied to a device, the

CylancePROTECT Mobile

app stopped responding and closed instead of displaying an alert that the OS was not supported. (UESAPP-4012)

On devices with

iOS

16.2, if a user enabled SMS message filtering, the feature was turned off after the user upgraded the app. (UESAPP-3764)

If a user sent the

CylancePROTECT Mobile

app to the background, then brought it to the foreground again, it could take up to 10 minutes for the app to check the device for threats. (UESAPP-3638)

For

CylancePROTECT Mobile

devices configured for Intune integration, if a user had not completed the

Microsoft

Online Device Registration process and snoozed the notification for one hour, the notification did not display again after one hour if the

CylancePROTECT Mobile

app was not running in the background. The user had to wait for the notification that would display every 24 hours. (UESAPP-2583)

If the

CylancePROTECT Mobile

app detected more than one threat, after you resolved one of the threats, a notification for a new threat still displayed on the device even though no new threats had been detected. (UESAPP-2553)

When a user tried to deactivate the

CylancePROTECT Mobile

app, in certain circumstances the deactivation could fail and cause the app to stop responding. (UESAPP-2228)

If a device security threat was detected and resolved, the device security section of the app might have still displayed a threat alert. (UESAPP-2224)

When a user deactivated the

CylancePROTECT Mobile

app, there was no dialogue to indicate that deactivation was in progress. (UESAPP-2167)

When a user activated the

CylancePROTECT Mobile

app, for the options under the text "No QR code?", the user had to tap the icon for the option and could not tap the text. (UESAPP-1886)

After activating the

CylancePROTECT Mobile

app, when the user was prompted to ignore battery optimization settings, a "This setting is not supported" error displayed. The user could close the error and allow the app to run in the background, but a message continued to display in the app reminding the user to allow it to run in the background. (UESAPP-3533)