
Build a release version of your add-on (it’ll be code signed automatically)ĩ. Set up code signing in your project: “Automatic”, “Team”, and “Signing Certificate: Development” are importantĨ. Security add-generic-password -a 'AC_USERNAME' -w 'AC_secret_pass' -s 'AC_PASSWORD_HOLDER’ĪC_USERNAME is the email of the identity to be used for notarization (AC = AppStore Connect)ĪC_secret_pass is that account’s passwordĪC_PASSWORD_HOLDER is a keychain which stores this info.ħ. Note that you don’t have to enable the hardened runtime, because it is not required for add-ons, and it’s not easy to setup the proper entitlements anyway.
(I guess most of you have already done this, so I don’t go into any detail here) The easiest way to do that is to add your developer account in Xcode / Preferences / Accounts.
Get your code signing identities for Developer ID: Application & Mac Developer
Set up the App Manager role for a developer (or add a special account with a separate email address)ģ. Enroll in the Apple Developer program (yes, the paid one, see this forum thread). You’ll have to perform a similar process if you ship installers or any accompanying tool or application It is also advisable to complete the process for add-ons for earlier Archicad versions as well. bundle) on macOS, then you’ll have to codesign and notarize your add-ons to make them work correctly on Catalina. So, if you want to distribute your add-on in its pure form (i.e. Your users will see a dialog similar to this: If that verification fails for some reason then Archicad won’t be able to load your add-on, even though Archicad 23 is set to load non-codesigned add-ons without complaining. This informs the operating the system that the downloaded file may contain malicious code, and so the operating system tries to verify the identity of the developer to ensure the user’s safety. When you download anything on macOS from the internet, the download mechanism adds extra info to the downloaded file (called the quarantine flag you can check for it with ls.