By default, Xcode Server signs binaries using a development certificate, not a distribution one. Unfortunately there is no built-in option to make it use a Developer ID certificate. What’s the solution?
Notarization is a fully automated process, unlike going through the App Store which involves manual human review. At least it’s automated in Apple’s side. However it could consume a non-negligible amount of brain bandwidth in your side. How about automating it?
Continuous testing is paramount to ship serous software. Yet continuously running tests is a pensive productivity plight. Is it possible to automate testing? Yes you can.
Xcode 13 brought a new notarization tool. What is it and how much better compared to the old one?
“I want a REST API for notarization since it’s impossible to parse text coming from the notarization tool reliably.” What if I say that the command line API is the best method for integration with build pipelines? Read on to find out more.
Notarization may take just a few clicks in Xcode, but this takes time and a security risk. You include notarization as part of your continuous delivery pipeline. Here’s how.
Distributing binaries for macOS outside the App Store requires registering it with Apple beforehand—notarizing it. But do you know what can be submitted for notarization?
Including passwords into the source tree is a big security breach. Similarly including passwords into build jobs would be insecure. Learn how to securely provide Apple ID credentials into notarization jobs.