> notarytool authenticates using a stored keychain profile that you create once, interactively — it prompts for an app-specific password, and there’s no way aro

> notarytool authenticates using a stored keychain profile that you create once, interactively — it prompts for an app-specific password, and there’s no way around the prompt. You can use `--password <password>` (yeah, yeah, passwords on the command line are bad; I'm just challenging "there's no way around the prompt.") Later (contradicting itself): > The one step that stays interactive is notarytool store-credentials, and that’s a choice rather than a limitation: you could pass --password and script it, but that means putting an app-specific password in your shell history. You can configure your shell to ignore history when needed. https://stackoverflow.com/questions/6475524/how-do-i-prevent-commands-from-showing-up-in-bash-history https://stackoverflow.com/questions/6475524/how-do-i-prevent... https://superuser.com/questions/352788/how-to-prevent-a-command-in-the-zshell-from-being-saved-into-history https://superuser.com/questions/352788/how-to-prevent-a-comm... (And if it's in a script, it won't be in your history anyway.) > These passwords go stale silently whenever you change your Apple ID password You can use an ASC API key instead. This can be either a team key ("developer" access level) or an individual key. https://developer.apple.com/documentation/appstoreconnectapi/creating-api-keys-for-app-store-connect-api https://developer.apple.com/documentation/appstoreconnectapi...