log error if signing cscInfo cannot be identified during signtool exe…

…cution. Return false for quick exit with logging

packages/app-builder-lib/src/codeSign/windowsSignToolManager.ts

@@ -34,7 +34,7 @@ export interface FileCodeSigningInfo {
 }
 
 export interface WindowsSignTaskConfiguration extends WindowsSignToolOptions {
-  readonly cscInfo: FileCodeSigningInfo | CertificateFromStoreInfo | null
+  readonly cscInfo: FileCodeSigningInfo | CertificateFromStoreInfo
 
   // set if output path differs from input (e.g. osslsigncode cannot sign file in-place)
   resultOutputPath?: string
@@ -194,6 +194,9 @@ export class WindowsSignToolManager {
         }
       }
       log.info(logInfo, "signing")
+    } else {
+      log.error(null, "no signing info identified, signing is skipped. Was this intentional? You can test further with `forceCodeSigning: true` in `win` configuration")
+      return false
     }
 
     const name = this.packager.appInfo.productName
@@ -412,7 +415,7 @@ export class WindowsSignToolManager {
     let args: Array<string>
     let env = process.env
     let vm: VmManager
-    const vmRequired = configuration.path.endsWith(".appx") || !("file" in configuration.cscInfo!) /* certificateSubjectName and other such options */
+    const vmRequired = configuration.path.endsWith(".appx") || !("file" in configuration.cscInfo) /* certificateSubjectName and other such options */
     const isWin = process.platform === "win32" || vmRequired
     const toolInfo = await this.getToolPath(isWin)
     const tool = toolInfo.path