Released: Jul 17, 2024

Updates in 2024 R1

Features

• Added the ability to use 'Custom Signing' to leverage other signing technologies in addition to those provided out of the box.
• Added new 'IATextPane' control in custom code panels to display large static text.
• Added the ability to capture invalid JVMs via a new exit code.
• Added a new option to store exit code from 'Execute Ant Script' action.
• Passwords passed in Get password action are now available as encrypted in installvariable.properties.
• Added a new command line argument to set the Temp directory during installation.

Fixes

• On the Linux platform, setting the IATEMPDIR variable failed to disable an InstallAnywhere installer from using the system temporary directory for some activities.
• Navigating through the Pre-Install sequence led the installer to hang and display the StackOverflowError on the console.
• The Create JRE VM Pack Wizard failed to create a VM pack from an extracted macOS JRE since Java 9 and displayed the Please choose a valid path for jre error message.
• An installer corrupted the $USER_INSTALL_DIR$ variable by deleting the files and failed to extract additional files via the Expand Archive (7-zip) action.
• If a user name ended with an exclamation mark, the installer would fail to launch with the Couldn't find the InstallScript to run the installer from! Unable to load the script. error message.
• An installer with the Extract Archive action was failed to retrieve source files’ timestamp from a .zip archive on a Linux machine, which resulted in the display of File OverWrite prompts for each file extracted from the archive.
• InstallAnywhere failed to pick up Java files from the Java Home folder and instead picked up Java files from the Internet Plug In folder, which led to an unsuccessful application installation.
• When the custom icon of an uninstaller was changed, the uninstaller application launch failure was observed on macOS Ventura/Sonoma.
• The Expand Archive (7-zip) action failed to extract a file to the directory specified by the IATEMPDIR environment variable.
• A crash was observed with 1067 error, when using Java 21 and later versions and launching a console launcher registered as Windows Services.
• InstallAnywhere installer failed to launch in silent mode on a target machine that was running in the Hebrew locale.
• When two duplicate files were included in a project, the installer installed the one file at the correct size and the other at 0 bytes.
• Japanese characters that were copied to the InstallAnywhere Graphical User Interface (GUI) led to the display of unknown characters.
• Files in the SpeedFolder with a defined filter failed to install in the Add feature type of maintenance mode.
• Inadequate permission for the /tmp directory usage and the InstallAnywhere installer’s failure to effectively utilize the directory specified by the IATEMPDIR environment variable, led to an installation failure with "unlicensed version" error message.
• The gradle process usage in the jar files signing led the installer to be installed with errors.
• A failure was observed when attempting to accept the Enter key as the default option during console mode uninstallation with the maintenance mode enabled.
• When a machine was connected to a LAN, InstallAnywhere generated the license file based on the LAN adapter MacID instead of the machine MacID.
• A build appliance failed and displayed the Message: Credential Information is specified, but it is incomplete. error message.
• A signed custom code action failed during runtime due to the addition of more than 20 dependencies.
• An installer failed to install the files and folders in the expected location via the Install from Manifest action.
• A failure was observed on the links usage that are included in the product documentation to access the javadocs.
• The Other Java-Enabled platforms build target customizer based installer failed to launch with Java 21.
• A failure was observed while testing the Oracle database connection on the Oracle 19C.
• The files failed to appear in the JavaDoc folder.
• The Java vendor name watermark was appeared during console mode Installation.
• Using the Set Windows Registry - Multiple Entries and Set Windows Registry - Single Entry actions failed to revert the DWORD values.
• The Password field in the response file was recorded empty after silent installation.
• The lax.nl.java.compiler LAX property was listed in the uninstaller lax file.
• When a customized installer title image icon included source path variables, a Merge module project failed to import to the parent project with the IAScript.loadScript() error.