The state of the art for integrating notarization into CI seems to be "oh just run that XCode tool in a loop until it says Apple has accepted your binary -- oh and btw its output is not designed to be machine-parseable lol".
-
-
Show this thread
-
"After uploading your app, the notarization process typically takes less than an hour. When the process completes, you receive an email indicating the outcome." Oh cool let me add an IMAP client into my Buildbot I guess!
Show this thread -
Someone asked me for another example of macOS CI related stupidity. Let's start with the obvious one: I have to violate Apple's EULA to run my CI on macOS without hosting a physical Mac somewhere. No VMs! In 2019. Or the $100/y to be allowed the privilege to develop for macOS.
Show this thread
End of conversation
New conversation -
-
-
pass --output xml at the end of the altool command to get a machine parsable version (parsing via PlistBuddy is recommended)
-
Err, --output-format xml I believe both work, but output-format is the option name in the altool man page and altool help (if you run altool with no options)
End of conversation
New conversation -
-
-
Just wait until you enable Apple Pay on a multitude of domains running Let's Encrypt certificates... You get an e-mail every 2 weeks to re-upload their meaningless validation files. When asked about automation, they claim they're not aware it's a problem.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.