Posts

Post not yet marked as solved
7 Replies
1.2k Views
As with most modern development practices, I want to automated notarization as part of my build pipeilne. I find two things horribly developer un-friendly with notarization as currently implemented. 1. We need a web service, not a command line. A web service that I can automate, one that has clearly defined outputs, Today, I have to parse text on the return from the command line, and there is no spec on what will be returned, which means I have a bunch of trial and error to handle all the edge cases, and makes the process brittle. The text could be changed at any time, and break automation.2. We need a notaration test endpoint. I don't want to officially notarize something and have Apple create an entry into the gatekeeper servers, and I don't need to staple. I want to submit builds regularly from my build pipeline to ensure that I have not introduced anything that does not meet notarization requirements. To meet corporate security requirements, we need to lock down the ability to notarize an app, which makes it more difficult to plumb this into the build pipeline. Having a test notarization endpoint that I could hit that would not require the username and passkey, that would allow us to submit builds for notarization readines would solve this problem. When it came time for release, submitting the final build through an official notarization endpoint would be a formality, because we've been testing it throughout the dev lifecycle.
Posted Last updated
.