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.

Facing error while building electron for windows 10

See original GitHub issue

22.7.0:

Electron Version:7.2.3
Electron Type (current, beta, nightly): current

Target: windows 10

Done Adding Additional Store\r 
 Error information: "Error: SignerSign() failed." (-1073700864/0xc000a000)\r 
  
 SignTool Error: An unexpected internal error has occurred.\r 
  
     at C:\\projects\\sttm-desktop\node_modules\\builder-util\\src\\util.ts:129:16 
     at ChildProcess.exithandler (child_process.js:301:5) 
     at ChildProcess.emit (events.js:198:13) 
     at maybeClose (internal/child_process.js:982:16) 
     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5) 
 From previous event: 
     at runCallback (timers.js:705:18) 
     at tryOnImmediate (timers.js:676:5) 
     at processImmediate (timers.js:658:5) 
 From previous event: 
     at WinPackager.signApp (C:\\projects\\sttm-desktop\node_modules\\app-builder-lib\\src\\winPackager.ts:374:27) 
',

Issue Analytics

State:
Created 3 years ago
Comments:7 (1 by maintainers)

Top GitHub Comments

1reaction

alex-dowcommented, Jul 24, 2020

I switched the timestamp url to http://timestamp.sectigo.com/?td=sha256 and my builds are working now.

{
  win: {
    ...
    rfc3161TimeStampServer: "http://timestamp.sectigo.com/?td=sha256"
  }
}

1reaction

DonMcNamaracommented, Jul 23, 2020

I think I was able to get around this by setting rfc3161TimeStampServer (docs) in the windows build configuration in package.json, but I’m not sure if I was hitting the same issue as you.

It looks like the debug flag is being used when signtool.exe is called, but I wonder if adding the verbose flag would give us better information.