-
-
Notifications
You must be signed in to change notification settings - Fork 366
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
Github Actions MacOS 11 build fails even with --no-sign option #946
Comments
Thanks for the report; it's a little difficult to confirm as you've only provided a 3 line snippet of the log, rather than the full build log - but it appears the issue is with the signing of the app, not the DMG. This isn't related to #865; that's about changing the interpretation of the signing options, rather than changing anything about what is signed. I can also confirm that signing can work - Briefcase's CI signs apps (including a PySide app) as part of the build process. Three suggestions to try in your case:
|
@freakboy3742 I tested with multiple versions: |
@victorswed It's impossible to diagnose a problem when you haven't provided any details about the failure; if you're having a problem, please open a new ticket, with the full failure logs output by Briefcase.
|
Describe the bug
When building in Github Actions on MacOS 11, the build goes well until the very end, but there is fails even when using the
--no-sign
option.#865 seem related but the app should still build and work on Mac OS 11 as before, or did I miss something?
To Reproduce
Example workflow action: https://github.com/gambhiro/pyqt6-build-example/blob/main/.github/workflows/briefcase_build.yml
From the build log:
Expected behavior
I used to use briefcace 0.3.7, and the MacOS 11 build was working with
--no-sign
. It would build the .dmg in Github Actions, and the user could add the app in Applications, although having to explicitly allow it to run in their security preferences (due to the unknown developer warning).Environment:
The text was updated successfully, but these errors were encountered: