About DrewSE

DrewSE · ‎Oct 14, 2020

Nevermind - this is the dark-mode issue. Switching MacOSX to Light appearance before running the installer resolves the issue.

DrewSE · ‎Oct 14, 2020

When launching my latest installer on MacOSX, it shows the splash screen then shuts down. Digging into the installer app and running the installer from the command line, I get the following stack trace: java.awt.IllegalComponentStateException: The frame is decorated at java.desktop/java.awt.Frame.setBackground(Frame.java:989) at Flexeraat7.setBackground(Unknown Source) at com.zerog.ia.installer.AAMgr.initAAMgr(Unknown Source) at com.zerog.ia.installer.LifeCycleManager.a5(Unknown Source) at com.zerog.ia.installer.LifeCycleManager.executeApplication(Unknown Source) at com.zerog.ia.installer.Main.main(Unknown Source) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at com.zerog.lax.LAX.launch(Unknown Source) at com.zerog.lax.LAX.main(Unknown Source) InstallAnywhere 2020 Running installer on MacOS 10.15.7 (Catalina) VM Pack: OpenJDK11U-jdk_x64_mac_hotspot_11.0.7_10.vm

DrewSE · ‎Jul 09, 2020

Christophe, Yea, that's a problem too. I worked with Flexera Support to build figure this out and end up using a script that he provided. The basic recipe is below: Copy OpenJDK11U-jre_x64_mac_hotspot_11.0.7.10.tar.gz to an empty directory Extract the .tar.gz file to that directory Make a directory named jre Move the Contents directory from the extracted .tar.gz file (jdk-11.0.7+10-jre/Contents) to the jre directory (jre/Contents) Make another directory named jre in the just moved jre/Contents/Home directory (jre/Contents/Home/jre) Copy everything inside the jre/Contents/Home directory to the inner jre directory (jre/Contents/Home/jre) Delete jre/Contents/MacOS/libjli.dylib Create a link in it's place: jre/Contents/MacOS/libjli.dylib --> jre/Contents/Home/jre/lib/jli/libjli.dylib But then, the VM Pack Wizard doesn't handle the symbolic link... thus the need for a script to zip everything up. I'll forward this message to the Flexera Support person I was talking to and ask him to post the script. -Drew

DrewSE · ‎Jun 30, 2020

After working with Tony (of Flexera Software Support), I've gotten notarization working! Yay! Our conversation is recorded in case number 02081289. I believe this ticket was a duplicate or a rephrasing of the ticket that spurred case 02081289. In other words, feel free to close this ticket. Thanks

DrewSE · ‎Mar 31, 2020

I'm having a heck of a time getting Apple Notarization to work with InstallAnywhere 2020. I've entered (what I think are) the right values into IA, but the resulting installer is refused by the Apple Notarization service. (I get errors like "The binary is not signed with a valid Developer ID certificate." and "The signature does not include a secure timestamp.") Is there a reference example that shows how to get code-signing and notarization working starting from just a .jar and a Developer ID Application certificate?

DrewSE · ‎Mar 30, 2020

Can anyone provide a step-by-step guide to using Apple Notarization in InstallAnywhere 2020? I've got a pile of .cer and .p12 files, four different kinds of certificates, application-specific passwords, and so on. I've also got a pile of command xcrun commands to try to debug my problems... but the best I've been able to manage is "Package Invalid" failure from Apple's notarization service. They're reporting errors like "The binary is not signed with a valid Developer ID certificate." and "The signature does not include a secure timestamp." I'd love to see a step-by-step guide that I can use to create SSCCE. Something like: Create a new blank project Download your Developer ID Application certificate Click here Click there Click build Notice no errors Run this command to validate the notarization

DrewSE · ‎Sep 10, 2014

Upon rebooting my Mac for an unrelated issue, aliases for my test product appeared in the Dock. I've been able to reproduce this behavior, but not deterministically. It seems to be related to some combination of: 1) Installing over an existing install 2) Rebooting the machine My attempts to reproduce the solution using `killall Dock`, `killall Finder`, and logoff-logon cycles don't seem to work. Even with this work arounds, I don't want to have to tell my users to restart their machines just to get the alias to appear in the Dock. A real solution would be appreciated.

DrewSE · ‎Sep 10, 2014

When I select the Mac OSX Dock as the target for my alias, the alias never appears in the dock. I've repeated this behavior with a SSCCE which is attached ( ). I believe this is item IOA-000081101 from the InstallAnywhere 2013 Known Issues list, but is not reported on the InstallAnywhere 2014 Known Issues list 1. Is this a known issue in InstallAnywhere 2014? 2. Is there a workaround? Thanks, Drew

Online Status	Offline
Date Last Visited	‎Sep 14, 2022 07:24 PM

Re: Installer silently fails to launch on MacOSX

Installer silently fails to launch on MacOSX

Re: Example of Apple Notarization

Re: Step by step to Notarization?

Example of Apple Notarization

Step by step to Notarization?

Rebooting and over-installing may workaround

Shortcut not added to Mac OSX Dock