I have a build script I have used for years that packages my app and builds the installer via a Jenkins build server. This script now fails when building the installer during the digital signing phase. Here is a redacted copy and paste of output:
Code: Select all
AdvancedInstaller.com /rebuild setup.aip
Checking builds status... done.
Build required.
[ DefaultBuild ]
Building package (en):
C:\work\workspace\windows-installer\installer\Setup Files\App-5.0.0_setup.exe
Preparing files... done.
Signing files from project... The digital signing of some files failed. Error Message:Certificate: Subject[XXX, Inc.] Issuer[DigiCert SHA2 Assured ID Code Signing CA]
digisign.exe error. Signing file. HRESULT: -2147024703. Error message: %1 is not a valid Win32 application.
digisign.exe sign /a /sha256 /d App Name /du http://www.acme.net/products/app /t http://timestamp.verisign.com/scripts/timstamp.dll APPDIR\bin\admin.exe APPDIR\bin\version.exe APPDIR\bin\gen_test_char.exe APPDIR\bin\happ2dbm.exe APPDIR\bin\app-stats.exe APPDIR\jre\bin\jp2launcher.exe APPDIR\jre\bin\ssvagent.exe APPDIR\jre\bin\pack200.exe ...lots more filenames
I tried changing my setup script to turn off digital signing completely. I then used the digisign tool in my build script to sign the EXE. That all worked fine (both the build and the signing), but whenever I run the installer on a test system the install ends without any logged errors of consequence (Error code 12) when it gets to the point where it would normally start performing the install. In other words, the installer runs through my wizard but when it starts to do something it just ends. If I run from command line and use the /exelog I just see that error code 12 in the output.
So I am going back to trying to do the signing as part of the setup.aip file. If I build via GUI, I can run installer fine. It is only when building via a command line script I have these problems.
Ideas?
Thanks
Mark
FOLLOW US
Get the latest news in Application Packaging