"External cannot be load due to macOS quarantine"
Hello everyone,
I am using a new M1 MacBook Pro and everything seems to works fine except for the externals.
I saw a post here from 2020 in the forum where they used this command in Terminal:
codesign --remove-signature /path/to/binaryAppName
https://reverseengineering.stackexchange.com/questions/13622/remove-code-signature-from-a-mac-binary
Doing this for the whole Bach library seems to be a lot a work.
Is there any newer work around or any new tip for doing fixing that?
It is telling to remove xattr com.apple.quarantine and not signature.
open terminal type
xattr -cr and drop whole bach folder on it
hit enter
Thanks a lot!
I'm trying to do the same with the aka. .mxo files but it doesn't seem to work for me in Big Sur? any other tips?
aka externals are 32 bit only, so no chance to run them on Big Sur
Ah! I hadn't considered that
I think Cycling74 should help with the upkeep of externals like aka. It seems like it wouldn't take much to approach the developers when an update breaks something. I've seen free externals like these hugely broaden the user base of Max over the last 20 years, particularly in visual arts and education.
Have you considered contacting the developer directly? That often works wonders, and it's a chance to thank them personally for their work.
I'm working on a Mac M1 and trying to use the shell object (external). I've tried opening terminal, typing "xattr -cr" then dragging the folder for the external to it. I get the response below and more, but I am not computer literate enough to understand what I should type to get shell (or any other external) to work.
Any help appreciated! Jawnypants
"
johnreed@IPEF-Laptop ~ % xattr -cr/Users/johnreed/Documents/Max\ 8/Packages/shell
xattr: invalid option -- /
usage: xattr [-l] [-r] [-s] [-v] [-x] file [file ...]
xattr -p [-l] [-r] [-s] [-v] [-x] attr_name file [file ...]
xattr -w [-r] [-s] [-x] attr_name attr_value file [file ...]
xattr -d [-r] [-s] attr_name file [file ...]
xattr -c [-r] [-s] file [file ...]
The first form lists the names of all xattrs on the given file(s).
The second form (-p) prints the value of the xattr attr_name.
The third form (-w) sets the value of the xattr attr_name to the string attr_value.
The fourth form (-d) deletes the xattr attr_name.
The fifth form (-c) deletes (clears) all xattrs."
as first :
johnreed@IPEF-Laptop ~ % xattr -cr/Users/johnreed/Documents/Max\ 8/Packages/shell
you forgot to insert space before dragging the shell into terminal window.
I would prepend sudo to ensure execution with admin privileges.
sudo xattr -cr /Users/johnreed/Documents/Max\ 8/Packages/shell
once fixed that should remove any xattr from the shell external
but depending on what you want shell to execute, you might again hit the wall
of macOS security.
@Gregory Taylor. Max MSP is a commercial product and pretty expensive. Are you suggesting we go cap in hand to these developers to work unpaid? My point is that it should be a commercial priority of Cycling 74.
While we do our best to assist developers by providing them with the tools to develop their own externals, we've never presumed to exercise any authority over the result or engage in anything that looks even remotely like exercising any control over the work they do.
When the developers of third-party objects come to us with questions (usually via the Forum or Customer Support) resulting from OS updates or substantial changes to Max, we always try to be helpful, but we do not make it a habit to disturb their daily developing lives; the person who develops the code or the package owns the results, and they make the decision about extending or updating their code as is their wont.
Perhaps if you were to be more specific about the object(s) you're unable to use, folks here might have some suggestions as to how to proceed. You may find a kindred soul who's found a substitute or a workaround they're willing to share with you. But I definitely drop a line to Akamatsu-san, if only to thank him for his generosity. I have yet to meet a developer who doesn't like being thanked.
My point is that Cycling 74 should be giving Akamatsu-san more than a pat on the head. Max MSP isn’t an open source effort, it’s been benefitting financially from the efforts of people like Akamatsu-san. It’s pretty clear that interest from 3rd party developers to make these plugins is now diminishing. I think Cycling74 should be looking very seriously at ways to change.
@Audio Source, thanks for your help, but shell.mxo still comes up orange as an object and gives this message in the Max Console "shell: could not load due to incorrect architecture". I made sure that the shell.mxo that I was using was the one that I applied the "sudo xattr -cr " to (and made sure there was a space before the path). Any other/further suggestions? I did re-start Max just to make sure it rescanned those folders... I appreciate your help, j
architecture is wrong- means you have non native shell version on M1
https://github.com/jeremybernstein/shell/releases/
take 1.0.3
Hey all,
typing it here for those privileged owners of newish MacBooks who are not being able to run patches because of "incorrect architecture" and "quarantine" (myself 10 min ago).
1. open your "get info" on Max application and check "open using rosetta"
2. in the quarantine window (screenshot above) click "proceed" and "apply to all"
worked for me, MacBook Air, Monterey, M1
xattr -d com.apple.quarantine /path/to/file worked for me on M1 - Sonoma 14.6.1