-
-
Notifications
You must be signed in to change notification settings - Fork 375
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
Code Signing Error #1891
Comments
I was able to reproduce this error. Be sure that PySide-Addons is being packaged. |
Regarding the specific suggestion: Briefcase had support for the It would be interesting to see if moving the frameworks from the Resources folder to the Frameworks folder (which is where Frameworks should live) resolves the issue. If it does, a macOS processing step that moves frameworks wouldn't be too difficult to add. Another possibility is to explicitly not sign Frameworks (on the basis that they should already be signed by the original distributor). |
That's the correct configuration. I only mentioned |
The issue appears to be related to the order of signing. Inside the PySide6 package is an embedded framework named
If you sign in this order, you get the error:
However, if you sign QtWebEngine Core last:
The signing process succeeds. It appears this is the only part of the Qt library that has this problem - if you manually do this signing sequence, then re-build (which re-signs everything), the signing of the app succeeds. Signing is currently done by grouping on the parent directory after sorting in reverse order, then signing everything in that directory in parallel. However, because the file name |
it solved!
thx, all of your help! |
Describe the bug
I'm using macbook pro 13inch(M1) with sonoma.
When using QtWebEngineCore with briefcase, code signing failed.
I fixed manually line 538 of
brieacase/platforms/macOS/__init__.py
like below, and worked fine.I think we need additional option for --deep or just add into process_command.
Steps to reproduce
Expected behavior
build complete and no other exceptions
Screenshots
No response
Environment
Logs
Additional context
No response
The text was updated successfully, but these errors were encountered: