-
-
Notifications
You must be signed in to change notification settings - Fork 131
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Notarizing the macOS binary to avoid the warning message #950
Comments
I had intended to write a Medium post about how I got this working, but then the pandemic intervened and totally wiped the details and plans from my brain. 😞 The first step is to get the binary signed and notarized locally on your development machine. Have you been able to do that? My signing experience isn’t going to be helpful because it centered on using Once you have that working, I can share the elements I needed to add to get notarization working, and how to do that inside of GitHub actions. The workflow that does it is here: https://github.com/Deep-Symmetry/beat-link-trigger/blob/master/.github/workflows/uberjar.yml You’ll want to focus on the |
Once you are ready to dig into those I can give more details about sections, and things that tripped me up, and how I configured the secrets needed for the workflow to sign things using my developer identity without leaking them to people who fork the repository. |
Since the binary isn’t registered with Apple, users will get a warning dialog.
It's possible to workaround this warning dialog but it would be better to notarize the binary: https://support.apple.com/guide/mac-help/open-a-mac-app-from-an-unidentified-developer-mh40616/mac
Fortunately, @brunchboy already did that on one project and can give us some tips yay! 😉
The text was updated successfully, but these errors were encountered: