pedrommcarrasco / Brooklyn

🍎 Screensaver inspired by Apple's Event on October 30, 2018

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Screen Saver can’t be opened because Apple cannot check it for malicious software.

jcannon23 opened this issue · comments

General troubleshooting

Before logging an issue please verify that:

If none of this fixes your issue, tell us more about it.

Required information

In order to help us sort your issue, we ask that you provide the following information:

  • Mac model:
  • macOS version:

Description of issue

After installing and following the directions to go into 'Security & Privacy' and then click 'Open Anyway' for the "Brooklyn.saver", I'm still receiving the error message “Brooklyn.saver” can’t be opened because Apple cannot check it for malicious software.
Screen Shot 2021-05-25 at 7 54 38 AM

Same issue on my side but if you are following the followed steps, it should work!

  1. Open Preferences
  2. Select Security & Privacy
  3. Select General
  4. On the bottom side, select Open Anyway

Works on:
macOS Big Sur 11.4
MacBook Pro (2019)

Im having same issue on MB Pro 16" with macOS Big Sur 11.5.2 appears that it needs to be updated.

@Onedah, use the steps that Azzuurro sent. It even works for my Macbook Air (2017) running 11.4 (20F71)!

Link: #95 (comment)

@Yb-G tried the steps but does not work on MacOS 11.52

You can bypass the click button solution by using this command to stop the apple macbook quarantine on the file in your terminal :

sudo xattr -d com.apple.quarantine ~/"Library/Screen Savers/Brooklyn.saver"

You can bypass the click button solution by using this command to stop the apple macbook quarantine on the file in your terminal :

sudo xattr -d com.apple.quarantine ~/"Library/Screen Savers/Brooklyn.saver"

Thanks the above worked.

@pedrommcarrasco, it would be better if you put the above command in a Troubleshooting section in the README.md file so it would help other people instead of finding for this issue! 😃

@pedrommcarrasco, it would be better if you put the above command in a Troubleshooting section in the README.md file so it would help other people instead of finding for this issue! 😃

Sounds good to me, please open a Pull Request with your suggestion!

@pedrommcarrasco, little reminder to check the PR ⬆️ 😉