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.

Code sign failed; please retry manually. Error: No identity found for signing.

See original GitHub issue

Hi,

Not sure if this is the correct place for this issue, however I’m getting the following error when attempting to build electron.

Is this a configuration issue, or perhaps a bug?

Installing production dependencies into Electron Build Package
electron-debug@1.0.1 tmp/electron-build-tmp/node_modules/electron-debug
├── electron-localshortcut@0.6.1
└── electron-is-dev@0.1.1
Installed and bundled electron-debug@^1.0.0
Installing Electron headers for version 1.1.2
Recompiling native dependencies
The cache parameter is deprecated, use download.cache instead
Packaging app for platform darwin x64 using electron v0.37.5
Code sign failed; please retry manually. Error: No identity found for signing.
    at /Users/mateodelnorte/development/cardstack-desktop/node_modules/electron-osx-sign/index.js:49:28
    at ChildProcess.exithandler (child_process.js:193:7)
    at emitTwo (events.js:106:13)
    at ChildProcess.emit (events.js:191:7)
    at maybeClose (internal/child_process.js:852:16)
    at Socket.<anonymous> (internal/child_process.js:323:11)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:188:7)
    at Pipe._handle.close [as _onclose] (net.js:492:12)

I’m on El Capitan version 10.11.5 (15F34) node --version: v6.3.0 electron --version: v1.3.1

Issue Analytics

State:
Created 7 years ago
Reactions:1
Comments:11 (4 by maintainers)

Top GitHub Comments

7reactions

barinalicommented, Sep 27, 2017

Hey, @sethlu,

I am currently trying to sign our application, but I am getting the same error as @mateodelnorte got. But I would like to indicate that when I run security find-identity on my CLI, it seems that I have two installed valid identities. If you have any idea about this situation, let me know.

4reactions

rasca0027commented, Dec 16, 2019

I’m not sure but this happened to me when I’m trying to use a wrong certificate to sign my .app file. I was using a Mac App Distribution cert which I believe is for signing .mas files for submission to Mac App Store. But since I was actually not distributing it in AppStore I was supposed to use the Developer ID Application Certificate instead. After I got the correct cert this problem is resolved! Hope this helps! (the image below shows the correct one to choose!) Screen Shot 2019-12-16 at 6 31 22 PM

Top Results From Across the Web

please retry manually. Error: No identity found for signing ...

I think your codesigning identities may not have installed in the default keychain so the signing tool has trouble looking for the signing...

"No identity found" error when codesigning app

In Keychain Access, I selected my Developer ID certificates and then had Keychain Access evaluate them. The Developer Application certificate is good for ......

codesign gives always no identity found error via terminal

codesign gives always no identity found error via terminal · Are you manually codesigning the app? If so, please show the entire codesign...

Identity not found when trying to code-sign an application with ...

Anyways, When I open the Keychain Access I see that certificate created in the System folder (with a + circle over it). Also,...

Command CodeSign failed with a nonzero exit code" error in ...

Solution · Click menu Product > Clean Build Folder while holding down option key or ⌘ - CMD + ⇧ - SHIFT +...