Skip to content
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

help !!! ''signature too large to embed '' this error when I sign my app #119

Closed
isNeilLin opened this issue Jan 8, 2017 · 12 comments
Closed
Labels

Comments

@isNeilLin
Copy link

Command failed: codesign --sign Developer ID Application: Beijing dream of micro literature Information Technology Co., Ltd. (RD7TJ35TVQ) --force /Users/neil/Downloads/快乐码字/快乐码字.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Libraries/libnode.dylib
/Users/neil/Downloads/快乐码字/快乐码字.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Libraries/libnode.dylib: signature too large to embed (size limitation of on-disk representation)

@sethlu
Copy link
Contributor

sethlu commented Jan 16, 2017

Hi @isNeilLin thanks for filing your issue! So far I have not encountered such situation but I'm currently trying to find a source to this issue... I will try to get back to this thread soon. 😄

Ref: https://opensource.apple.com/source/libsecurity_codesigning/
https://opensource.apple.com/source/security_systemkeychain/

@sethlu
Copy link
Contributor

sethlu commented Jan 16, 2017

@isNeilLin would you mind displaying a copy of your entitlements file? I'm afraid that it may be oversized for embedding in your app.

@legikaloz
Copy link

I'm facing this issue too when I try to build and sign with electron-builder. My entitlements file:

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
  <dict>
    <key>com.apple.security.app-sandbox</key>
    <true/>
    <key>com.apple.security.network.client</key>
    <true/>
    <key>com.apple.security.application-groups</key>
    <string>xxxxxxxxxx.com.yyyyyyy.zzzzzzz</string>    
  </dict>
</plist>```

The problem persist even when I use default entitlements file.

@sethlu
Copy link
Contributor

sethlu commented Feb 4, 2017

@isNeilLin @legikaloz I'm not very sure what causes codesign to have such behavior... Would you like to try having your app in all ASCII characters first and see if it works with codesigning?

@legikaloz
Copy link

@sethlu Do you mean the app name? My app name contains [a-z,A-Z] but can't sign the dmg.

@sethlu
Copy link
Contributor

sethlu commented Feb 13, 2017

@legikaloz are you trying to call electron-osx-sign on the .dmg file?

@legikaloz
Copy link

@sethlu no, I'm trying to call it on my .app. Tried the workflow with electron-packager and electron-builder too. The mas package creation is always successful, i can upload the .pkg file to the iTunesConnect. The dmg creation process constanly fail even with a new certificate.

I've seen a workaround in a SO topic. This method is maybe (temporary) applicabe?
http://stackoverflow.com/q/36960440

@sethlu
Copy link
Contributor

sethlu commented Feb 21, 2017

Hi @legikaloz sorry for my late reply. Would you mind providing a signing/packaging log that I may refer to? I am not very sure around which step we are encountering this issue as the mas package creation is always successful.

@legikaloz
Copy link

@sethlu I've attached a build log:
versions:
electron 1.4.15
electron-builder: 14.1.1

dmgSignError.txt
npm-debug.txt

@sethlu
Copy link
Contributor

sethlu commented Feb 25, 2017

@legikaloz I believe this should be an issue directly from codesign. As we are still fairly inconclusive with the situation, we can probably just continue investigating where the issue comes from.


An potential idea is from the --timestamp option; by disabling the timestamp service may we complete the code signing process. There should be a more elegant way to correctly sign the app bundle I think. I will look into this a bit more over the weekend, codesign_allocate can be a possible start to some solution...

@sethlu
Copy link
Contributor

sethlu commented Apr 14, 2017

@legikaloz would this be a duplicate of #64 (comment)?

@isNeilLin
Copy link
Author

@sethlu
Sorry, just to see your reply。
I have solved this problem by manually signing the way。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants