Barrier: Catalina : Can’t be opened because Apple cannot check it for malicious software

Created on 29 Mar 2020 · 4Comments · Source: debauchee/barrier

Operating Systems

Server: MacOS Catalina

Client: MacOS Catalina

Barrier Version

2.3.2

Steps to reproduce bug

Install on Macbook from DMG
On launch, get subject dialog, "Can’t be opened because Apple cannot check it for malicious software." Move to Trash or Cancel.

Other info

~This is not caused by attribute com.apple.quarantine.~
This is probably caused because the application is not signed.
$ codesign -dv /Applications/Barrier.app/Contents/MacOS/barrier /Applications/Barrier.app/Contents/MacOS/barrier: code object is not signed at all
~I cannot overcome this because it's a work laptop with group policies.~
If the assembly was signed, I could probably overcome an unknown publisher.
Does this bug prevent you from using Barrier entirely? ~Yes~ No

Source

the-reverend

Most helpful comment

Right click on Barrier under Applications in Finder and click open.
You'll get a dialog with an option to open.
Works for me whenever I run into the old " Apple cannot check it for malicious software" problem.

andydna on 1 Apr 2020

👍8 🚀1

All 4 comments

update: actually, i was able to overcome this by removing the com.apple.quarantine attribute.
so i guess i'm leaving this open as a suggestion to sign the application.

the-reverend on 29 Mar 2020

andydna on 1 Apr 2020

👍8 🚀1

This issue has been automatically marked as stale due to inactivity. It will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] on 26 Sep 2020

Right click on Barrier under Applications in Finder and click open.
You'll get a dialog with an option to open.
Works for me whenever I run into the old " Apple cannot check it for malicious software" problem.

This worked great for me. It seems like best option for any cases like this on MacOS.

Although my need was for MacOS Big Sur beta (local) to control TwisterOS (remote, Raspberry Pi) and I suppose I'll have to research why the 'local' trackpad/cursor affects the local machine as well as the remote.