From aa460b1b195383897cc1a06440ac8213837ec137 Mon Sep 17 00:00:00 2001 From: Niklas Wenzel Date: Fri, 30 May 2025 02:18:01 +0200 Subject: [PATCH] docs: update debugging note for Azure Trusted Signing --- guides/code-signing/code-signing-windows.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/guides/code-signing/code-signing-windows.md b/guides/code-signing/code-signing-windows.md index 15e7210..36a1ac8 100644 --- a/guides/code-signing/code-signing-windows.md +++ b/guides/code-signing/code-signing-windows.md @@ -78,7 +78,7 @@ Then install the dependencies for local code signing as described [here](https:/ In your project directory, do the following: 1. Install the `dotenv-cli` package: `npm i -D dotenv-cli` -2. Update `@electron/windows-sign` to version 1.2.0 or later: `npm update @electron/windows-sign` +2. Update `@electron/windows-sign` to version 1.2.2 or later: `npm update @electron/windows-sign` #### Creating the `.env.trustedsigning` file @@ -144,7 +144,9 @@ Some notes: We specify the `/v` and `/debug` parameters even though they aren't technically required. This ensures that warnings are logged if timestamping fails. -**Do not** use the `debug` parameter on the `WindowsSignOptions`. Similarly, **do not** enable the `DEBUG` environment variable for `electron-windows-sign`. (If you do either of them, the `debug` npm package will log all debug messages to stderr. An executable in `@electron/windows-sign` will interpret the existence of messages printed to stderr as a signing failure. Then your build will fail.) +{% hint style="info" %} +Set the environment variable `DEBUG` to `electron-windows-sign` to get verbose debug output while signing. +{% endhint %} #### Adjusting your `forge.config.ts`