InstallAnywhere 2024 R1
The following issues have been fixed in InstallAnywhere 2024 R1:
|
Issue Number |
Issue Summary |
|
IA-15956 |
On the Linux platform, setting the IATEMPDIR variable failed to disable an InstallAnywhere installer from using the system temporary directory for some activities. This issue has been fixed. |
|
IA-21340 |
Navigating through the Pre-Install sequence led the installer to hang and display the StackOverflowError on the console. This issue has been fixed. |
|
IA-20888 |
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. This issue has been fixed. |
|
IA-20644 |
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. This issue has been fixed. |
|
IA-21575 |
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. This issue has been fixed. |
|
IA-21059 |
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. This issue has been fixed. |
|
IA-21647 |
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. This issue has been fixed. |
|
IA-21646 |
When the custom icon of an uninstaller was changed, the uninstaller application launch failure was observed on macOS Ventura/Sonoma with the following message: [Name of the app] is damaged and can't be opened. You should move it to the Trash. This issue has been fixed. |
|
IA-21177 |
The Expand Archive (7-zip) action failed to extract a file to the directory specified by the IATEMPDIR environment variable. This issue has been fixed. |
|
IA-21690 |
A crash was observed with 1067 error, when using Java 21 and later versions and launching a console launcher registered as Windows Services. This issue has been fixed. |
|
IA-21413 |
InstallAnywhere installer failed to launch in silent mode on a target machine that was running in the Hebrew locale. This issue has been fixed. |
|
IA-21607 |
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. This issue has been fixed. |
|
IA-21586 |
Japanese characters that were copied to the InstallAnywhere Graphical User Interface (GUI) led to the display of unknown characters. This issue has been fixed. |
|
IA-21351 |
Files in the SpeedFolder with a defined filter failed to install in the Add feature type of maintenance mode. This issue has been fixed. |
|
IA-16850 |
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. This issue has been fixed. |
|
IA-21375 |
The gradle process usage in the jar files signing led the installer to be installed with errors. This issue has been fixed. |
|
IA-21460 |
A failure was observed when attempting to accept the Enter key as the default option during console mode uninstallation with the maintenance mode enabled. This issue has been fixed. |
|
IA-21649 |
When a machine was connected to a LAN, InstallAnywhere generated the license file based on the LAN adapter MacID instead of the machine MacID. This issue has been fixed. |
|
IA-21212 |
A build appliance failed and displayed the Message: Credential Information is specified, but it is incomplete. error message. This issue has been fixed. |
|
IA-15766 |
A signed custom code action failed during runtime due to the addition of more than 20 dependencies. This issue has been fixed. |
|
IA-21622 |
An installer failed to install the files and folders in the expected location via the Install from Manifest action. This issue has been fixed. |
|
IA-21642 |
A failure was observed on the links usage that are included in the product documentation to access the javadocs. This issue has been fixed. |
|
IA-21573 |
The Other Java-Enabled platforms build target customizer based installer failed to launch with Java 21 and led to display the following error message: Exception in thread "main" java.lang.NoClassDefFoundError: java/lang/Compiler at install. This issue has been fixed. |
|
IA-21473 |
A failure was observed while testing the Oracle database connection on the Oracle 19C. This issue has been fixed. |
|
IA-21650 |
The files were failed to appear in the JavaDoc folder. This issue has been fixed. |
|
IA-21620 |
The Java vendor name watermark was appeared during console mode Installation. This has been removed. |
|
IA-12257 |
Using the Set Windows Registry - Multiple Entries and Set Windows Registry - Single Entry actions failed to revert the DWORD values. This issue has been fixed. |
|
IA-21299 |
The Password field in the response file was recorded empty after silent installation. This issue has been fixed. |
|
IA-21621 |
The lax.nl.java.compiler LAX property was listed in the uninstaller lax file. This has been removed |
|
IA-21014 |
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. This issue has been fixed. |