This article discusses the "invalid entry size" build warning that occurs when building on the command line.
Symptoms
If your project contains a "Create LaunchAnywhere for Java Application" action, a non-Windows build target has been selected to be built, and the build is performed through the command line, then you may notice the following message in the build log:
invalid entry size (expected <size> but got <size> bytes)
where <size> references a size value in bytes. Note that this warning message should not appear, but it can be safely ignored.
Cause
This problem has been reproduced and determined to be an issue in our software. This issue has been submitted to our Engineering team as Issue# IOA-000063382. Our Engineering team is investigating this issue, but at this moment, there is no estimated time frame for when it will be fixed. There is a workaround available below.
Steps To Reproduce
Create a new InstallAnywhere project
Go to Sequence tab > Install and add a "Create LaunchAnywhere for Java Application" action
Go to Build tab and select a non-Windows build target, e.g. Linux
Save and close the project
Build the project through the command line, e.g. build.exe <Project_File_Path>
Observe that the build log generates the "invalid entry size" message
Workaround
The build warning message is safe to ignore and should not cause any build time or runtime issues.
We have purchased InstallAnywhere2022. license in April. I am getting this issue "invalid entry size (expected 87092 but got 65536 bytes) " when i am building installer.
And as a result of this issue incomplete installer exe is getting generated. It is not able to generate all screen in exe. And this is severe issue as major screens are eliminated and we cannot achieve successful operation.
This build error should not have any effect on the resulting installer. If you are seeing issues with the installer, please open a Support Case to track that. We will be able to assist you better working through a Support Case. Thanks!
