Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Unsigned Mac binary leads to warning message "The application is damaged..." #555
TL;DR - Just type this in at the Terminal (change
I'm putting this here to highlight that this is a known issue and also to discuss the possibility of signing the Mac Archi binary.
The issue is due to Gatekeeper on MacOS. If an app that is not signed is run on a Mac it can lead to one of two error dialog messages:
“Archi can’t be opened because it is from an unidentified developer.”
This is easy to solve by Control-click or by right clicking the app and selecting “Open” from the contextual menu that appears, then click “Open” in the dialog box.
Or the message may say:
"Archi is damaged and can’t be opened. You should move it to the Trash."
Normally one can solve this by following these instructions.
However, on MacOS Catalina (10.15) users are getting the "Archi is damaged..." message even after applying the
This can be solved by following these instructions.
One thing to note - this last case applies to Archi 4.6 but not Archi 4.5.1. I don't know why this is. Perhaps something to do with Archi 4.5.1 using Eclipe 4.11 and Archi 4.6 using Eclipse 4.13.
The information on how to solve this issue is present:
However. some users miss this information and they then report the issue. (I can't blame them for that, users shouldn't have to deal with this).
To solve this problem we could sign the Mac binary.
To sign an app we need to:
There is no way to test this process without committing to $99. I'm not even sure if it will work.
I am averse to this for many reasons, the main one being that I dislike that we have to pay Apple to distribute free and open source software. We don't have to do this for Windows or Linux.
What would be ideal is if someone who has an Apple Developer account could do a test to see if signing the Archi.app is possible before we commit to this. If they could do that and let us know what they did that would be very helpful. :-)
This process is horribly complicated and I'm not sure if it can be automated.
If Archi Mac users would like to see this done, then they might consider helping out with this. Until then things will remain as they are and it is up to end-users to apply the workaround outlined above.
For an individual user the "quarantine bit" workaround is do-able but an inconvenience. An organization or company that may not be able to do this has the option of building from the source code and creating their own binary distribution, or perhaps signing the existing binary with their own certificate and distributing that internally.
Fortunately, Archi is open source and free and so there are many options, including contributing to solve this issue.
Nothing else to suggest. You have to ensure the path to the Archi.app is correct: