Fix for plugin "cannot be opened because developer cannot be verified" error

Macintosh software/hardware discussion and troubleshooting

Moderator: James Steele

User avatar
James Steele
Site Administrator
Posts: 22786
Joined: Fri Oct 15, 2004 10:01 pm
Primary DAW OS: MacOS
Location: San Diego, CA - U.S.A.
Contact:

Re: Fix for plugin "cannot be opened because developer cannot be verified" error

Post by James Steele »

Just an update to this thread. If you don't want to use Terminal there's a freeware app called Sentinel that I think is for apps but it works on plugins as well. You drag and drop on to the app's window and it will remove the app or plugin for quarantine.

https://github.com/alienator88/Sentinel/releases

Screenshot 2024-11-13 at 4.39.25 PM.png
Screenshot 2024-11-13 at 4.39.25 PM.png (87.96 KiB) Viewed 2313 times


The only difference I see when using it is after you use it, checking it in terminal with the xattr command will return "com.apple.provenance" Not sure what that means, but it works. If you're nervous about that you can still use the terminal command. I'll probably just stick with Terminal since this situation doesn't arise often except with plugins from very small developers.
JamesSteeleProject.com | Facebook | Instagram | Twitter

Mac Studio M1 Max, 64GB/2TB, macOS Sequoia 15.5 Public Beta 2, DP 11.34, MOTU 828es, MOTU 24Ai, MOTU MIDI Express XT, UAD-2 TB3 Satellite OCTO, Console 1 Mk2, Avid S3, NI Komplete Kontrol S88 Mk2, Red Type B, Millennia HV-3C, Warm Audio WA-2A, AudioScape 76F, Dean guitars, Marshall amps, etc., etc.!
Post Reply