Codesing Command failed : signature too large to embed (size limitation of on-disk representation)
See original GitHub issue- Version: electron-builder: 19.16.0 electron: 1.4.13
- Target: OSX
Error: Command failed: codesign --sign 386D1D89C204824F22337EC75275EE4168F1DB8A --force /Users/neil/Documents/MyAppName/happy/dist/mac/happycoding.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Libraries/libnode.dylib
/Users/neil/Documents/MyAppName/happy/dist/mac/happycoding.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Libraries/libnode.dylib: signature too large to embed (size limitation of on-disk representation)
at ChildProcess.exithandler (child_process.js:270:12)
at emitTwo (events.js:125:13)
at ChildProcess.emit (events.js:213:7)
at maybeClose (internal/child_process.js:897:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:208:5)
From previous event:
at Promise.longStackTracesCaptureStackTrace [as _captureStackTrace] (/Users/neil/Documents/MyAppName/happy/node_modules/.3.5.0@bluebird/js/release/debuggability.js:397:19)
at new PromiseSpawn (/Users/neil/Documents/MyAppName/happy/node_modules/.3.5.0@bluebird/js/release/generators.js:43:17)
at /Users/neil/Documents/MyAppName/happy/node_modules/.3.5.0@bluebird/js/release/generators.js:197:21
at build (/Users/neil/Documents/MyAppName/happy/node_modules/.19.16.0@electron-builder/out/builder.js:69:21)
at Object.args [as handler] (/Users/neil/Documents/MyAppName/happy/node_modules/.19.16.0@electron-builder/out/cli/cli.js:121:9)
at Object.self.runCommand (/Users/neil/Documents/MyAppName/happy/node_modules/.8.0.2@yargs/lib/command.js:233:22)
at Object.Yargs.self._parseArgs (/Users/neil/Documents/MyAppName/happy/node_modules/.8.0.2@yargs/yargs.js:1018:24)
at Object.get [as argv] (/Users/neil/Documents/MyAppName/happy/node_modules/.8.0.2@yargs/yargs.js:927:19)
at Object.<anonymous> (/Users/neil/Documents/MyAppName/happy/node_modules/.19.16.0@electron-builder/out/cli/cli.js:117:465)
at Module._compile (module.js:569:30)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:503:32)
at tryModuleLoad (module.js:466:12)
at Function.Module._load (module.js:458:3)
at Function.Module.runMain (module.js:605:10)
at startup (bootstrap_node.js:158:16)
at bootstrap_node.js:575:3
npm ERR! code ELIFECYCLE
npm ERR! errno 255
npm ERR! happycoding@4.1.2 dist: `build`
npm ERR! Exit status 255
npm ERR!
npm ERR! Failed at the happycoding@4.1.2 dist script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
Issue Analytics
- State:
- Created 6 years ago
- Comments:10 (2 by maintainers)
Top Results From Across the Web
signature too large to embed | Apple Developer Forums
It appears that when the application is re-signed by the export process the --signature-size=12000 attribute is not inherited. How can I work around...
Read more >Codesing Command failed signature too large to embed (size ...
codesign : signature too large to embed (size limitation of on-disk representation)今天同事新增一个模块之后codesign写的签名脚本出现这个bug,网上搜.
Read more >Developers - help !!! ''signature too large to embed '' this error when I ...
''signature too large to embed '' this error when I sign my app. ... Command failed: codesign --sign Developer ID Application: Beijing dream...
Read more >How to solve "Application failed codesign verification" when ...
I've got a problem that I couldn't solve with a deep search in different resources as most of the "similar" points out to...
Read more >Mac Codesign: signature too large to embed - CSDN博客
今天打包遇到一个问题,签名时遇到一个错误,signature too large to embed (size limitation of on-disk representation)通过网上搜索, ...
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
I’ve found here and here that the
--signature-size
option could help with this bug. I’ve tested it with my certificate, I picked a value of 12800, and it fixed this for me.@develar Do we get any solution of this signature issue currently?