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

[mateodelnorte]

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
[email protected] tmp/electron-build-tmp/node_modules/electron-debug
├── [email protected]
└── [email protected]
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

[sethlu]

Hi @mateodelnorte, would you try security find-identity in your Terminal and see if there being certificates available first?

[zoubir-remila]

Policy: X.509 Basic
Matching identities
0 identities found

Valid identities only
0 valid identities found

[sethlu]

@amazighezed If running the command displays:

Policy: X.509 Basic
Matching identities
0 identities found

Valid identities only
0 valid identities found

I think your codesigning identities may not have installed in the default keychain so the signing tool has trouble looking for the signing certificates. The wiki page at https://github.com/electron-userland/electron-osx-sign/wiki/1.-Getting-Started#certificates is pretty outdated, but it describes a brief way to obtain signing certs. After having them installed, you should be able to see a list of names available from running security find-identity.

[barinali]

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.

[sethlu]

Closing this issue for now since it's been inactive for quite a while.

[Chinmoy-globalIds]

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 one installed valid identities. If you have any idea about this situation, let me know.

[preethamsridhar]

Same problem. I dont know why anybody is replying even though electron-osx-sign has so many weekly downloads

[sethlu]

@preethamsridhar Are you having the same issue that no signing identities are showing up? (You may also this with security find-identity -p codesigning -v.) If no certificates are showing up for your target distribution “3rd Party MAC Developer Application” for MAS and “Developer ID Application” otherwise, you’ll need to first obtain them from the Apple Developer dashboard.

[theanhmx]

Last time i have this issue the certificate was expired, even though it still show up on the terminal. Hope this help

[rasca0027]

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!)

[marcj]

@barinali then specify which to use using --osx-sign.identity="IDENTITY2"

➜ security find-identity

Policy: X.509 Basic
  Matching identities
  1) asdasd "Mac Developer: asdada@asdasd (IDENTITY1)"
  2) asdads "Developer ID Application: asdada2@asdasd (IDENTITY2)"
     2 identities found

  Valid identities only
  1) asdasd "Mac Developer: asdada@asdasd (IDENTITY1)"
  2) asdads "Developer ID Application: asdada2@asdasd (IDENTITY2)"
     2 valid identities found