-
-
Notifications
You must be signed in to change notification settings - Fork 354
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
Cannot code sign on Big Sur MacOS #1818
Comments
I am looking further into this issue. Currently, this StackOverflow post suggests that "This problem happens when I verified that
|
Interesting - Briefcase should be verifying that all the necessary tools are available, including differentiating between Xcode and the Command Line Tools. I've just done a test on my M1 Mac, and it looks like it is possible to use the command line tools to sign; I wonder if this might be an x86-related incompatibility. Although the SO post mentions the specific install order, I don't think the order of installation is likely to be the cause - this should only be triggered be the tools that are currently active. |
Continuing to dig, I found the following page on PyInstaller which explains an issue with PyInstaller that produces the same error message.
I'm not sure whether this is directly relevant. |
Current guess based on discussion during the sprint: Something in the format of the template being produced by recent versions of Xcode are incompatible with the code signing tools from the older versions of Xcode. Next steps:
|
If anyone is still facing issue even after checking XCode and iCloud Drive, the following worked for me! Steps to follow:
This worked like a charm! Happy Coding! |
@nidhikamath2102 To clarify - the issue you were seeing (CRLF handling) is a different way to manifest the same error message. The PyCon sprints have revealed at least 3 ways that signing can fail:
These are all distinct issues, with different solutions - although they all manifest with the "Unable to code sign" error message. |
I was unable to build the stub project from the Mac OS app template on my machine, as described in this issue: beeware/Python-Apple-support#220 |
Describe the bug
When following the BeeWare tutorial on a Big Sur MacOS (x86_64), the
briefcase build
command is unable to code sign.Steps to reproduce
briefcase create
briefcase build
briefcase build
command fails with the following error:Notably, the command
Produces the following result:
Expected behavior
The ad-hoc signing should complete without issue.
Screenshots
No response
Environment
Logs
briefcase.2024_05_20-16_37_34.build.log
Additional context
No response
The text was updated successfully, but these errors were encountered: