xcnotary
hubomat
Our great sponsors
xcnotary | hubomat | |
---|---|---|
2 | 1 | |
648 | 3 | |
- | - | |
1.5 | 5.9 | |
almost 2 years ago | about 3 years ago | |
Rust | JavaScript | |
MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
xcnotary
-
[Weekly] What is everybody working on? Share your progress, discoveries, tips and tricks!
I'm about 50 browser tabs deep into macOS signing. This is a nice video (https://www.youtube.com/watch?v=91sTQ39kkK4) of how many steps you have to take for getting the certificate. I did some of them, and I'm not 100 sure if I clicked on the right things. I found a nice tool that does help with the automatic upload to apple once you have all the necessary thing for it (https://github.com/akeru-inc/xcnotary).
-
The Gates to Hell: Apples Notarizing
The notarization process is super painful, no doubt. I had originally written shell scripts to automate the process for my company, but recently switched to the excellent command line tool 'xcnotary' (https://github.com/akeru-inc/xcnotary). it's available through Homebrew.
hubomat
-
The Gates to Hell: Apples Notarizing
My advice from years of notarizing my apps is to make sure you do it at least once per day for each of your apps. If you only notarize once every release (say, every month or so), you are almost guaranteed to encounter some new cryptic error that you've never seen before, either due to some glitch in signing your app or frameworks, or else some server-side error such as new terms & conditions that you are being "encouraged" to agree to. It will take you hours to research and resolve them if they aren't spotted right away.
As others pointed out, https://github.com/mitchellh/gon is a great tool for doing this on your local machine (e.g., with a cron job). In addition, if you are building your app using a GitHub action (which I highly recommend if it is open-source), you can use my https://github.com/hubomatic/hubomat action to package and notarize a release in one shot. The sample/template app does this automatically on every commit as well as once per day: https://github.com/hubomatic/MicroVector/actions.
So when this fails from a scheduled job, you at least know that something has changed on the Apple side and can investigate that right away. And if it fails as a result of a commit, then at least you can start looking at what changes you may have made to your entitlements or code signing settings or embedded frameworks or any of the other million things that can cause it to fail.
What are some alternatives?
gon - Sign, notarize, and package macOS CLI tools and applications written in any language. Available as both a CLI and a Go library.
corona - Solar2D Game Engine main repository (ex Corona SDK)
fruity - Rusty bindings for Apple libraries
divvunspell-sdk-swift - A Swift wrapper around DivvunSpell
MicroVector - Native macOS SVG viewer
dsdump - An improved nm + Objective-C & Swift class-dump
alacritty - A cross-platform, OpenGL terminal emulator.