-
Notifications
You must be signed in to change notification settings - Fork 283
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
Make it possible to run qssign
outside of CI
#2868
Comments
Makes sense. We'll continue to get some error message upon opening because the DMG won't be signed -- we don't have local credentials for that (which is a different kind of signature than that used for the app itself). Currently a Debug build can be transferred to another computer and run without any signing at all, but at least on MacOS 12.3 the detection that it is a downloaded file leads to a "this app is broken" error with no obvious GUI workaround. CLI-savvy users can I think the easiest / best approach is to add a flag for configuration to When I run as: $ SIGNING_IDENTITY='ABCD' Tools/qsrelease Debug It correctly produces a Debug build, including a DMG that I've transferred to my wife's computer and run. There is the expected dialog requiring one to cmd-click and open (which has been documented before, due to unsigned DMG) but no "broken application" error as one gets with a completely unsigned build. It runs and shows it is indeed a debug build as expected. |
Much simpler, I didn't realise I could just run I'm wondering now if we should build a release and debug build on every commit, or just a release build? |
I wouldn't anticipate much benefit in adding debug builds to CI; we're likely all already running debug builds locally while we develop. Except... if we take a "random" example: https://github.com/quicksilver/Quicksilver/actions/runs/2291220282 If I changed the Yeah that might be worth doing. And it makes it so having the |
Kind of interesting, the output in CI:
So it looks like |
Also use `uname -m` instead of `arch` to determine host architecture. Fixes #2868
It would be great if we were able to sign our own builds locally using
qssign
. A use case is that I want to build a debug version of the app, or I want to run a signed version of the debug app for testing.Right now, it seems possible, with a few mods to the qssign script. Here's what I had to do:
I think that was it. It would be great if the
qssign
script could detect where it's being run, and do this itself though!@n8henrie - I'm hoping this is an issue you can handle :D
The text was updated successfully, but these errors were encountered: