Build Error When Building a InstallAnywhere Project through a 3rd-Party Application Like Visual Studio

[#1]

Summary

This article discusses a build error that is generated when building an InstallAnywhere project through a 3rd-party application, like Visual Studio, that does not have digital signing configured.

Symptoms

This article discusses a build error that is generated when building an InstallAnywhere project through a 3rd-party application, like Visual Studio, with the command-line builder when digital signing is not configured.

The command-line builder returns a -1 exit code, which is interpreted as a build failure by Visual Studio, and generates this build error message in the verbose build log:

<Warning>Code signing failed with following error: Unable to sign</Warning>

Cause

Digital signing is not configured in the InstallAnywhere project.

Steps To Reproduce

1. Create a project.
2. Make sure not to configure digital signing.
3. Enable verbose build logging.
4. Build the project using the command-line builder.

Resolution

This issue has been accepted by the Engineering Team as a valid Bug for tracking with Issue# IOJ-1830666. There is no estimated timeframe for the resolution of this issue but addressing the issue is being considered for a future release.

Workaround

1. Configure digital signing in the project.
2. Write a wrapper script to handle the -1 exit code from the command-line builder so that this specific case does not get interpreted as a build failure by the 3rd-party application, such as Visual Studio.
3. Redirect the verbose build log output to a log file so the build error is not captured by the 3rd-party application, such as Visual Studio.

Additional Information

For more information about generating a verbose build log when building on Windows and Linux, click here.

For more information about generating a verbose build log when building on Mac OS X and macOS, click here.