Electron-builder: Windows code signing on Mac OSX with Paralles installed

[aytek]

• Version: 19.45.0

• Target: Mac

I have Paralles Desktop Pro installed with an EV certificate on my Mac (with a USB dongle plugged in)
When trying to sign the win build on Mac, it always fails. I see the following errors on the command line.

Error: Exit code: 2. Command failed: prlctl exec {**user_id**} --current-user \\Mac\Host\\Users\user\Library\Caches\electron-builder\winCodeSign\winCodeSign-1.9.0\windows-10\x64\signtool.exe sign /t http://timestamp.globalsign.com/?signature=sha2 /sha1 **SHA1_CODE** /s **Store Name** /d **Product Name** /du **website_url** \\Mac\Host\\Users\user\electron\ft\release\win-unpacked\file_name.exe

    at /Users/user/electron/ft/node_modules/builder-util/src/util.ts:108:16
    at ChildProcess.exithandler (child_process.js:277:5)
    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)

...

When trying to sign the build on Windows it signs successfully but on Mac it always fail.
Here is my build script:

    "nsis": {
      "perMachine": true
    },
    "win": {
      "target": [
        "nsis"
      ],
      "certificateSubjectName": "My Certificate Subject Name",
      "timeStampServer": "http://timestamp.globalsign.com/?signature=sha2",
      "certificatePassword": "PASSWORD"
    },

And here is the build command
npm run build && build --win --ia32 --x64

Could be related with my Paralles configuration?

[develar]

Please set env DEBUG=electron-builder and attach log of the terminal output. If you want privacy — send me direct message in the Slack.

[develar]

I have Paralles Desktop Pro installed with an EV certificate on my Mac (with a USB dongle plugged in)

Please ensure that this dongle device is connected not to your mac, but to virtual machine.

[aytek]

@develar I have sent them 2 days ago, please check your Slack. Thanks.
And yes the dongle is connected to the virtual machine.

[develar]

@aytek I don't see direct message from you in the Slack (http://electron-builder.slack.com/).

[aytek]

@develar Okay I sent it to the correct Slack. Sorry.

[rjb8682]

Did this ever go anywhere? Running into this issue as well...

[johnryan]

@aytek did you ever figure this out?

[johnryan]

@rjb8682 did you ever get your EV signing working?

[rjb8682]

@johnryan I believe we did! And to be honest, for us it was just updating electron-builder and making sure parallels was running so the signing could be automatically started.

Also making sure to have the pro license for parallels instead of the lowest one. If you don't have pro or higher, the library to talk between the mac and parallels isn't available

[johnryan]

@rjb8682 thanks for the tip, I think i've done all that, including upgrading parallels. The Exit code: 2. Command failed: prlctl exec ... error is pretty vague...i might just try to reinstall parallels / windows 10.

[rjb8682]

@johnryan Yeah, sorry it wasn't much help! Hope you can figure it out, though

[johnryan]

Thanks to @develar for helping me debug...In the end my particular problem was that my parallels wasn't configured to access my windows drives correctly...here's a screenshot of the VM sharing configuration that worked:

[develar]

In addition, please note also, that "Share Mac user folders with Windows" must be not checked.

[mobitar]

Such a cool feature! I just tested this using the free version of Parallels and it works flawlessly.

Edit: I was indeed using the free trial, and I needed to upgrade after the free trial to keep this feature.

[damianobarbati]

@develar I'm still getting the following:

  • ensure that 'Share folders' is set to 'All Disks', see https://goo.gl/E6XphP
  • ensure that 'Share folders' is set to 'All Disks', see https://goo.gl/E6XphP
Error: Cannot cleanup: 

Error #1 --------------------------------------------------------------------------------
Error: Exit code: 255. Command failed: prlctl exec {aac0be65-f135-4bfc-b508-2cada07b8201} --current-user \\Mac\Host\\Users\damiano\Library\Caches\electron-builder\winCodeSign\winCodeSign-2.0.0\windows-10\x64\makeappx.exe pack /o /f \\Mac\Host\\Users\damiano\Desktop\tav-client\dist\__appx-x64\mapping.txt /p \\Mac\Host\\Users\damiano\Desktop\tav-client\dist\TAV-6.2.5.appx /nc

Is the pro version required? @mobitar did you use the free trial version?

[damianobarbati]

Furthermore: is this parallels builiding required if I'm not trying to sign the .appx (just store)?

[adunndevster]

Hmmm...
I have parallels pro installed
I'm using the settings above
Am using electron 4.1.0 and electron-builder 20.38.5
I'm running paralles, and have my EV token device plugged in.
I see that it is reading it fin in windows using SafeNet Auth Client

I'm getting this error: Please ensure that your are logged in "Windows 10" parallels virtual machine

Has anyone else seen this? Thanks for any help!

[Nealsoni00]

Also experiencing the same issue. I have the exact settings specified above by @johnryan.
I am using:
Electron-builder Version: 21.2.0
Electron Version: v6.0.4
Parallels Desktop Pro Version 15.1.2 (47123)

Any advice would be greatly appreciated, Thanks!

[johnryan]

@Nealsoni00 fwiw I switched to the jsign method in the docs a while back.

[klishevich]

Have the same issue. I am using:

• macOS Catalina: 10.15.2
• Parallels Desktop 15 for Mac Home Edition: Version 15.1.2 (47123)
• electron: 6.1.4
• electron-builder: 21.2.0

Changing Parallels preferences does not help. Switched to Windows for signing windows code :(

[zdQAQ]

@klishevich try upgrade electron-builder to a higher version. such as 22.2.0.

It's worked for me.