We have been using InstallAnywhere for many years to build the multiplatform installers for our product. Our product runs on Windows x64, AIX ppc64, Linux x64, and Linux s390x. InstallAnywhere has been working great on those system architectures until we upgraded to InstallAnywhere 2023 R2.
All of those 4 system architectures are supported with a single InstallAnywhere project file. We use one speedFolder action to pick up files at build-time from a folder of a specific architecture. We use separate speedFolder actions in the order of Windows x64, AIX ppc64, Linux x64 and Linux s390x. With this approach, all files are installed properly on the target platforms with all versions of InstallAnywhere up to 2022.
When the project file is upgraded to InstallAnywhere 2023, the speedFolder actions for Windows, AIX and the first Linux architecture (in our case Linux x64) in the project file still work fine. However the speedFolder for the second Linux architecture (Linux s390x) does not. Many files were installed as zero byte files. If two speedFolder action order is reversed with Linux s390x first and Linux x64 second, Linux s390x files are now installed with proper sizes, but many files for Linux x64 are now zero bytes.
Has anyone seen this problem? Is this a known issue?
Yes, this is a known issue in our product. Newer JRE versions/Java 21 have included additional integrity checks for .zip files with zip64 extra fields validation, and the files generated by the installer were affected by this, which led to duplicate files included in the installer not being copied properly. One file was installed as the correct size, and the other is installed as 0 bytes. This issue has been addressed in the latest release, InstallAnywhere 2024 R1. Hotfix is also available for this issue for InstallAnywhere 2023. Please upgrade to InstallAnywhere 2024 R1 or contact support for the hotfix.
Yes, this is a known issue in our product. Newer JRE versions/Java 21 have included additional integrity checks for .zip files with zip64 extra fields validation, and the files generated by the installer were affected by this, which led to duplicate files included in the installer not being copied properly. One file was installed as the correct size, and the other is installed as 0 bytes. This issue has been addressed in the latest release, InstallAnywhere 2024 R1. Hotfix is also available for this issue for InstallAnywhere 2023. Please upgrade to InstallAnywhere 2024 R1 or contact support for the hotfix.
Thank you for the reply. We observed that the 0 bytes problem still persisted with IA2023 and JDK 11 and 17. We also observed with IA2022 and JDK 21, the problem did not occur.
We contacted the support and got the hotfix. With the hotfix, the problem is now resolved with IA2023.
