Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
nested code is modified or invalid
See original GitHub issueI’m trying to sign my app for release outside of the app store and the signing always fails to verify.
My npm script runs electron-packager --osxSign.identity='Developer: Developer Name (<ID>)' which I understand uses electron-osx-sign to sign the app. Verifying the signing fails with nested code is modified or invalid.
I’ve attached the debugger output which includes my npm script.
Not sure if I’m missing any steps.
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
nested code is modified or invalid · Issue #131 - GitHub
I'm trying to sign my app for release outside of the app store and the signing always fails to verify. My npm script...
Read more >OS X codesign nested code is modified or invalid
create a folder called A inside versions with same contents of 4, change the symbolic links to the A folder especially current->A.
Read more >OSX Code signing nested code is modified or invalid
OSX Code signing nested code is modified or invalid. We are building an installer using Installbuilder 21.12.0 on Mac OS X 10.14.6 Mojave....
Read more >Signature not accepted? | Apple Developer Forums
The most common cause for problems like this is incorrectly nested code. You must follow the rules outlined in the Nested Code section...
Read more >Problems with code signing - General - Xojo Forum
Tried again using the very same terminal commands to code sign my app as well as the internal ... nested code is modified...
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 Free
Top 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
After hours of hair pulling, I finally found the root cause. I was manually setting the codesigning option in KeyChainAccess to Always Trust for my DeveloperID Application certificate. Removing this option and have it use the system defaults was all that was required.
@twvm That resolved it for me! So glad to have this working. Thanks for making such an awesome package!