InstallAnywhere 2014 Known Issues
SummaryThis article contains a list of known issues, workarounds, hotfixes, and related information for InstallAnywhere 2014. The article will be updated as new information becomes available.
SynopsisThis article contains a list of known issues, workarounds, hotfixes, and related information for InstallAnywhere 2014 and InstallAnywhere 2014 SP1. The article will be updated as new information becomes available.
|IOJ-1665770||Mac OS X authenticated launchers created with InstallAnywhere 2014 do not launch.|
|IOJ-1663318||If authentication is enabled in two or more OS X-based installers and an end user tries running these installers simultaneously, the authentication prompts for administrator name and password may not be displayed. Thus, standard users may not have adequate privileges to complete either installer.|
|IOJ-1663773||If authentication is enabled in an OS X-based installer, the files that were extracted to the $TMPDIR and /tmp locations are not deleted by the installer or the uninstaller.|
|IOJ-1664183||The Execute Uninstaller action does not uninstall a product from OS X-based systems if authentication was enabled in the original installer.|
In addition, if an upgrade attempts to uninstall an earlier version of a product before installing the new version on an OS X-based system, and if authentication is enabled in the base version of the product, the upgrade cannot successfully uninstall the earlier version or install the latest version.
|IOJ-1664447||If authentication is enabled for OS X-based installers and launchers, the run-time panels do not respond to any keyboard events. As a result, end users must use the mouse to click and select controls such as buttons and radio buttons. VoiceOver, the built-in screen reader that is available on OS X-based systems, cannot read the text on the run-time panels.|
This appears to be a bug in Java rather than in InstallAnywhere, since the same issue occurs with a Swing-based Java application. The InstallAnywhere team has reported the bug to Oracle.
To work around the issue and enable end users to enter text for run-time panels, whenever an end user clicks a text box, a native dialog box opens, enable the end user to enter the appropriate text. When the native dialog box is dismissed, the text that the end user entered is displayed in the text box that the end user had clicked on the run-time panel. To avoid displaying the native dialog box at run time, set the new variable $IA_BLOCK_OSX_USE_SECURE_POPUP_DIALOG_FOR_AUTHENTICATION$ to *yes* or *true*.
|IOJ-1664588||The strings for some of the controls on the Tomcat Runtime Deployment panel may be truncated on the Japanese version of this panel:|
?Choose button--If the Local Tomcat server option is selected on this panel, the panel includes a Choose button next to the Local Tomcat server path setting. Part of the text on the Choose button is cut off on the Japanese version of this panel.
?Test Connection button--If the Remote Tomcat server option is selected on this panel, the panel includes a Test Connection button. Part of the text of the Test Connection button is cut off on the Japanese version of this panel.
?Save the WAR locally on the target system for later deployment option--If this option is included on this panel, part of the last character in the label for this option is cut off.
|IOJ-1664649||The Always Show GUI setting is available under the Authentication setting (Project Page > Platforms view > Mac OS X area). If you select Yes for this setting, InstallAnywhere's built-in Authentication panel is not displayed at run time.|
(InstallAnywhere's built-in Authentication panel has the text "You need an Administrator password to install the software" and a lock icon that end users need to click to display the standard OS X-based credentials prompt.)
|IOJ-1665180||The InstallAnywhere 2014 installer or any installer created using Installanywhere 2014 that is not located at least 3 folders deep fails to launch on a *nix platform when run as root.|
|IOJ-1665716||If an uninstaller created with InstallAnywhere 2014 is run as root on a *nix machine, the uninstaller fails to launch.|
|IOJ-1663251||Rules on Install Sets intermittently do not execute causing Install Sets to be available on the Choose Install Sets Panel which should not be.|
InstallAnywhere 2014 SP1 Known Issues:
|IOA-000125033||Java applications that are launched using a Java 7 graphical LaunchAnywhere cannot write to relative paths on Apple OS X-based systems in some scenarios, such as when the application is launched by double-clicking it from within the Finder. As a workaround, the application can be launched from the executable stub within the .app structure, or you can offer a Console launcher.|
|IOJ-1662464||Under certain conditions, a LaunchAnywhere launcher that is installed on an OS X-based system and using Java 7 cannot find and load a required native library that is installed to $USER_INSTALL_DIR$.|
|IOJ-1664319||A graphical LaunchAnywhere launcher that is installed on an OS X-based system and using Java 7 cannot access a file that is in the same folder as the launcher and is referenced by a relative path. The problem does not exist for the console launcher, or if an absolute path is used to reference the file.|
|IOJ-1699420||OS X-based, code-signed installers that include authentication support do not create uninstaller shortcuts.|
|IOJ-1718753||If a CD-ROM installer that targets OS X-based target systems installs merge modules, the merge modules cannot be uninstalled from the $USER_INSTALL_DIR$ directory where the merge module is located.|
|IOJ-1719020||Maintenance mode and instance management do not work as expected for CD-ROM installers that target OS X-based target systems. For example, an attempt to try to manage an existing installed instance and remove a feature leads to the installer to stop responding.|
|IOJ-1699908||When an installer includes an imported merge module and Red Hat Package Management (RPM) registration is enabled in the merge module, it takes much more time to install and uninstall the merge module on Red Hat Enterprise Linux 7 systems then it does for earlier versions of Red Hat Enterprise Linux.|
|IOJ-1700753||If you add authentication support to an OS X-based installer and an end user runs the installer on an Apple OS X 10.10 target system, the installer launches a second time and then exits; this occurs after the end user clicks Done for the initial run of the installer.|
|IOJ-1700997||The About dialog box in InstallAnywhere on OS X-based versions shows version 1.0 of InstallAnywhere instead of 16.5 for InstallAnywhere 2014 SP1.|
|IOJ-1720113||In certain scenarios, the default icon is used in the Finder instead of a custom icon for the uninstaller launcher on OS X-based target systems. This occurs if the custom icon file is for a merge module that includes authentication support. The custom icon is displayed in the Dock only when the uninstaller is running.|