chipjarred

Also I noticed that someone edited your question to remove the `swift` and `appkit` tags - which is correct given the current state of the question, but if you end...

Also something that might make a difference, which I haven't noticed until now since I'm for now stuck on Big Sur, but I just found out that Apple has *deprecated*...

Thank you for the kind words, and I'm glad to know it was helpful to you in fixing your build script issues. I'll need to do some more thinking about...

@toonetown I like your suggestion about keying off of Developer ID. It sounds like you have a clear idea and are more recently in the depths of code signing details...

Great! I look forward to seeing it.

That error indicates SMJobBless failed. The most likely cause is that your app is sandboxed, which doesn't support privileged helper tools. So make sure you remove the sandbox capability from...

@abstertee Regarding removing the sandbox, you do that by clicking on your project in Xcode's project navigator (side-bar on the left that shows files and folders). That will bring up...

@abstertee It's set up to work with `"Mac Developer:"` and `"Apple Development:"`, which I *think* are what `SMJobBless` (or maybe it's `launchd`) needs to launch the helper tool. But I...

@abstertee What follows involves editing your Info plists. I recommend using a plain text editor for this particular task rather than plist editor for this (so not Xcode). I'm using...

@abstertee Once you've gotten a working build, if you want to use a different certificate, you'll probably need to modify `CodeSignUpdate.swift` to use it. ```swift func isValidDeveloperCN(_ s: String) ->...