-
-
Notifications
You must be signed in to change notification settings - Fork 70
PR auto tests fail at "Install Cretificates for Code Signing" stage #906
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
Comments
Hey @Junology! Thanks for the report. Official macOS releases of Processing are signed and notarized during the automated build process. However, if you want to create your own custom builds of Processing to share with someone else, you will need to sign the code with your own certificates. This is because macOS won't allow apps from unknown developers to run. Instructions are available here: https://github.com/processing/processing4/blob/main/build/CODESIGNING.md If you just want to test your changes on your machine, it may be easier to build Processing locally: https://github.com/processing/processing4/tree/main/build (Note that we're working on simplifying the build process so this page may be changing soon). @Stefterv: feel free to correct me or add anything I missed. |
Yes, the secrets needed for building a signed version are hidden on PR because it is unverified code by third parties |
Hm, that may be confusing for contributors since it presents as failed checks. How about we make macOS unsigned builds for PRs? |
This should be fixed now, it will probably still fail if your branch is not up to date with main |
Most appropriate sub-area of Processing 4?
Build process
Processing version
GitHub Actions
Operating system
GitHub Actions
Steps to reproduce this
"1. Make PR
"
snippet
No response
Additional context
The tests fail at the stage before actual build, so maybe I have nothing to treat the errors.
Would you like to work on the issue?
I am glad if core maintainers could fix the issue.
The text was updated successfully, but these errors were encountered: