“libchromescreenai.so” can’t be opened because Apple cannot check it for malicious software.

[paro-paro]

Description

Since yesterday I am getting a macos pop-up warning every time I open brave.

Steps to reproduce

1. Open brave browser

Actual result

Expected result

Do not get any warning.

Reproduces how often

Easily reproduced

Brave version (brave://version info)

1.70.126 Chromium: 129.0.6668.100 (Official Build) (arm64)

Channel information

• release (stable)
• beta
• nightly

Reproducibility

• with Brave Shields disabled
• with Brave Rewards disabled
• in the latest version of Chrome

Miscellaneous information

No response

[helloromero]

+1

[rebron]

@paro-paro @helloromero Can you update to the latest 1.71.114 and let us know if you're still seeing the issue.
Also, what version of macOS are you running? macOS 15 Sequoia?

[S30tt]

@paro-paro @helloromero Can you update to the latest 1.71.114 and let us know if you're still seeing the issue. Also, what version of macOS are you running? macOS 15 Sequoia?

I've got the exact same issue and have the latest version installed. I am running Sonoma 14.7 (23H124).

[S30tt]

I could bypass the warning by manually allowing the lib to run but this is not the way.

[paro-paro]

Hi @rebron

I am on macos sonoma 14.1.1 and now on the latest brave version 1.71.114 which no longer displays the warning. The file is still downloaded but I guess is all fine now.

[marijnbent]

I have the same issue on Chrome

[bsclifton]

This is something shipped with Chrome / Chromium (see https://issues.chromium.org/issues/40810109). I wonder if there is something we need to disable (via args GN or similar) if we don't want to include it?

cc: @cdesouza-chromium @emerick @mkarolin

For folks wanting to get rid of the message, you can try to delete the file in question. It should be a path like:
/Users/{username}/Library/Application Support/BraveSoftware/Brave-Browser/screen_ai/125.0/libchromescreenai.so

You can delete the screen_ai folder and you should be good to go

[jiripospisil]

Debian removes it. Brave should too.

https://salsa.debian.org/chromium-team/chromium/-/commit/ee2d7017ed0b99a27f5b763ee782fdd8a0999660

[bsclifton]

Looks like this is being tracked upstream with https://issues.chromium.org/issues/366284843 - which is a bit weird, since (for Chrome) the library should have the same signer as Chrome itself

[mherrmann]

It appears to be a Google component that is pulled in when the browser uses accessibility APIs. I get it when I turn on Speedreader. Redditors report getting it when using 1Password.

When I have the component, then it shows up in brave://components as ScreenAI Library.

[luispuerto]

I think this is a wide issue related to chrome based browsers. I'm getting the same with Vivaldi last version in macOS 15.1. I got the option to throw it to the trash and there is…

[kjozwiak]

The above requires 1.74.21 or higher for 1.74.x verification 👍

[MadhaviSeelam]

Verification PASSED using

Brave | 1.74.25 Chromium: 132.0.6834.33 (Official Build) beta (arm64)
-- | --
Revision | 041ffab11e000929213dcdae825dba438ff8a620
OS | macOS Version 14.6.1 (Build 23G93)

Couldn't reproduce the issue in 1.70.126 Chromium: 129.0.6668.100 (arm64) and 1.71.114 Chromium: 130.0.6723.58 (arm64) using STR from #41877 (comment)

• Installed 1.74.25

• launched Brave

• visited a website

• enabled Screen Reader

• logged in to 1Password

  • Confirmed no errors are shown upon starting Brave on macOS Sonoma 14.6.1.
  • Confirmed ScreenAI Library component is not shown.

example	example

[LaurenWags]

Removed QA Pass-macOS-arm64 as this was uplifted. Requires 1.73.102 or higher for verification 👍🏻

[LaurenWags]

Verified with

Brave | 1.73.102 Chromium: 131.0.6778.139 (Official Build) (x86_64)
-- | --
Revision | 6806ad35635fe0ddfd23411347211aa34c59a8d4
OS | macOS Version 14.7.2 (Build 23H311)

Using STR from #41629 (comment) and 1.70.126 Chromium: 129.0.6668.100, was unable to reproduce the issue.

Using same STR and 1.73.102 Chromium: 131.0.6778.139 confirmed that:

• no errors are shown upon starting Brave on macOS Sonoma 14.x
• ScreenAI Library component is not shown on brave://components
• no errors observed when using Speedreader

Example	Example

[MadhaviSeelam]

Verification PASSED using

Brave | 1.73.102 Chromium: 131.0.6778.139 (Official Build) (arm64)
-- | --
Revision | 6806ad35635fe0ddfd23411347211aa34c59a8d4
OS | macOS Version 14.6.1 (Build 23G93)

1. Installed 1.73.102
2. launched Brave
3. visited a website
4. enabled Screen Reader
5. logged in to 1Password
6. opened brave://settings/help

• Confirmed no errors are shown upon starting Brave on macOS Sonoma 14.6.1.
• Confirmed ScreenAI Library component is not shown.

example	example	example