-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to Code Sign on Windows #1596
Comments
Are you sure that your file is accessible (read permission for current user)? |
Yes I am - to be sure I just gave full permission to "everyone" and tried again. Still same problem. |
Please try 18.2.0 (it is next version, not visible on npm) — is your pfx file inside project directory — please try to set |
I have not tried 18.2.0 yet. But when I change the CSC_LINK as suggested I now get a different error: SignTool Error: An error occurred while attempting to load the signing
From previous event: |
18.2.0 and relative path support was fixed for you. Please try this version. |
I can only see 18.1.1 at https://github.com/electron-userland/electron-builder/releases |
Release will be announced when published as |
After updating to 18.2.0 - now I get the following error:
|
@daveywc Although this ain't seem to be the same issue that you have try to delete the spaces around the
|
@black-snow Ouch, it seems your are right, bloody, blooody windows. |
Woot!! We have a winner. No more errors. Thanks @develar and @black-snow. Appreciate all the help! |
@black-snow I have added @daveywc Thanks for donation :) |
You're welcome ;) Always glad to help develar with this great piece |
@develar How's that |
381e8c0#diff-adb7b90f249c915a5bdae8ff5be096f4R49
update: e63e8fa |
@develar I think the $50 donation is a small price to pay for all the work that you've put into this. Always happy to contribute. |
"electron-builder": "^18.1.0"
"electron-updater": "^1.16.0"
I have donated $50 USD as per above.
I have purchased a code signing certificate and converted it to pfx.
My build script is:
"ionic-app-scripts build && set CSC_LINK=C:\Data\Development\Projects\DocsOnTapV2\build\dotv2codesign.pfx && set CSC_KEY_PASSWORD=NotTelling && build"
However I get the following error indicating that it cannot find my pfx file. But the path is valid.
Rebuilding native production dependencies for win32:x64
Packaging for win32 x64 using electron 1.6.8 to dist\win-unpacked
Error: C:\Data\Development\Projects\DocsOnTapV2\build\dotv2codesign.pfx doesn't exist
at C:\Data\Development\Projects\DocsOnTapV2\node_modules\electron-builder\src\codeSign.ts:45:11
at next (native)
at runCallback (timers.js:651:20)
at tryOnImmediate (timers.js:624:5)
at processImmediate [as _immediateCallback] (timers.js:596:5)
From previous event:
at downloadCertificate (C:\Data\Development\Projects\DocsOnTapV2\node_modules\electron-builder\out\codeSign.js:49:21)
at Lazy.WinPackager.cscInfo.Lazy (C:\Data\Development\Projects\DocsOnTapV2\node_modules\electron-builder\src\winPackager.ts:42:9)
at Lazy.get value [as value] (C:\Data\Development\Projects\DocsOnTapV2\node_modules\electron-builder-util\src\util.ts:248:24)
at C:\Data\Development\Projects\DocsOnTapV2\node_modules\electron-builder\src\winPackager.ts:168:32
at next (native)
I have spent hours trying to find a solution without any success. I did try using keytool to convert the pfx to p12. Made no difference.
My development environment is Windows 10.
Kind regards,
David
The text was updated successfully, but these errors were encountered: