PR auto tests fail at "Install Cretificates for Code Signing" stage

[Junology]

Most appropriate sub-area of Processing 4?

Build process

Processing version

GitHub Actions

Operating system

GitHub Actions

Steps to reproduce this

"1. Make PR

2. The auto tests run and fail with error "At least one of p12-filepath or p12-file-base64 must be provided" from "Create Pull Request Build for macos (aarch64)"
   "

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.

[SableRaf]

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.

[Junology]

@SableRaf I encountered error not on my fork repository but exactly this repository; namely in #899 #905 .
I remember #873 was okay.

[SableRaf]

Ah thanks for the clarification! I just saw the failure in #905

There doesn't seem to have been a recent change to the build workflow. Hopefully @Stefterv will have an idea why this is happening.

[Stefterv]

Yes, the secrets needed for building a signed version are hidden on PR because it is unverified code by third parties

[SableRaf]

Hm, that may be confusing for contributors since it presents as failed checks. How about we make macOS unsigned builds for PRs?

[Stefterv]

This should be fixed now, it will probably still fail if your branch is not up to date with main