code object is not signed at all
See original GitHub issue- Version: 20.25.0
- Target: macos
When I build for windows using NSIS, I have no issue signing the app. However, when I try to build for macos, I get code object is not signed at all
because of my LICENSE.txt being in the Contents directory. It’s the same issue here: https://github.com/electron-userland/electron-builder/issues/2522
but it doesn’t seem like it was fixed
In my package.json, I have:
{
...
"build": {
...
"extraFiles": "LICENSE.txt"
}
}
I created an afterPack script to move the file myself but the same issue persists
Issue Analytics
- State:
- Created 5 years ago
- Comments:14 (1 by maintainers)
Top Results From Across the Web
macos - How do you fix "code object is not signed at all In ...
For me this problem was resolved by a simple "clean build folder" action, keyboard shortcut: shift+option+command+K. Share.
Read more >Getting "code object is not signed… | Apple Developer Forums
Getting "code object is not signed at all In architecture: x86_64" errors ... We're trying to submit our desktop app for gallery making...
Read more >code object is not signed at all · Issue #5549 - GitHub
framework: code object is not signed at all In subcomponent: /Users/osxserver/builds/3f61e126/1/frontend/vsignpdfui/release/mac/VSignPDF.app/ ...
Read more >Codesign states code object is not signed at all - Ask Different
codesign generally looks at only the specific object you told it to (exception: when you use the --deep option, it'll sign or verify...
Read more >Invalid Signature. Code object not signed at all... for iOS code ...
Code object is not signed at all... for binaries in the kivy and numpy paths. The project was built using the command line...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
My solution was simple, don’t use a file without extension. It seems to assume that without extension it is a binary that must be signed. I just changed my
LICENSE
file toLICENSE.txt
If you can’t do that, I’d suggest signing it manually with the
codesign
CLI tool, it’s really easy.When I manually codesign the executable file on Mac, I have this error message
main executable failed strict validation
with the following commandcodesign -f -v -s "Company Name" <executable file>