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)
',
have the same issue. this appears to be the solution, as I am using comodoca timestamp server
https://stackoverflow.com/questions/62161135/signersign-failed-2146869243-0x80096005
But not sure how I can add this argument
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.
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"
}
}
this only fixed my issue for one build. they are now failing again. I do notice that some things get signed then it failed with the same ambigious error.
I wonder if I'm getting rate limited.... but using --verbose flag told me nothing.
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
Doesn't https://github.com/electron-userland/electron-builder/pull/5147 fix this issue?
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.