Different method to notarize Plug-In

Question

Hi everyone,I was recently trying to notarize my plugins, and trying to notarize manually then running the following commands at the following link: https://helpx.adobe.com/nz/indesign/kb/indesign-plugin-notarization.htmlNotarizing in the following way I came across the following message given by the terminal "*** Warning: altool has been deprecated for notarization and starting in late 2023 will no longer be supported by the Apple notary service. You should start using notarytool to notarize your software .(-1030)"So searching on youtube I came across a video, where he explains how to notarize using notarytool, and in fact the notarization process is greatly simplified and watching other videos of his videos I realized that the notarization can take place directly via xcode using the "archive" function.Here comes my question "Why everyone uses terminal commands when they could easily use XCode "Archive"?? I personally haven't tried this method yet because I didn't know it existed and I've always done the notarization via terminal, so I wanted to ask if it was the same thing or if in my in case it doesn't go well.Another thing that i found inconvenient is the fact that every time i make changes to my Plug-Ins I have to renotarize all the plugins for all the indeisgn versions so from 2018 to 2023, there is a faster method to notarize the plugins togheter?This post wants to be a place where everyone knows all the methods to notarize a plug-in because I've lost a lot of time to understood it.P.S. I distribute the Plug-In via a package/installer How to notarize Plug-in without terminal: https://www.youtube.com/watch?v=fMRT8mPMJUsHow to notarize Plug-In with terminal (new method): https://www.youtube.com/watch?v=2xJcMzoi0EI

leo.r · Answer

Here comes my question "Why everyone uses terminal commands when they could easily use XCode "Archive"??

By @Stefano5C37

I can't say for everyone but I use terminal commands because they allow to fully automate the notarization process. Obviously, I'm not running them manually in Terminal. You can build your own droplet app that will run the terminal commands and do whatever else is needed to sign and notarize your apps. Then just drop your products on your droplet and everything will be done automatically. At least that's what I did.

I think that by now you can also find notarization automation solutions created by other developers, which may or may not suit your needs. Try to look them up. For example, DMG Canvas can notarize dmgs automatically. I only use my own tool as it's tailored to my specific workflow.

This can also help you re-notarize plug-ins faster when you release updates. Re-notarizing each individual product is unavoidable, there's no easier way to do this.

This post wants to be a place where everyone knows all the methods to notarize a plug-in because I've lost a lot of time to understood it.

You're not the only one I can tell you that. Many developers lost tons of time trying to understand Apple's convoluted, barely coherent notarization instructions. Especially back when Apple first introduced it several years ago. Now with the new notarytool the process is much easier. Compared to the do-it-yourself IKEA-style bag of disjointed tools that Apple dropped on developers in the beginning.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded