-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Launch Issues #7
Comments
Darn. Not sure what the issue is offhand. My own laptop completely crashed, needing a full restore from backup when I attempted the High Sierra upgrade, so I'll be putting off trying that again as long as possible. I'll take a look if I do get access to a High Sierra machine at some point. |
Any insight on this? Jarzilla crashes when I launch it from Finder, but I can launch it through terminal. ~/Applications/Jarzilla |
Found a similar issue here java-decompiler/jd-gui#147. Fixed my issue by changing the Jarzilla > Contents > Info.plist Under JavaX, I changed JVMVersion from 1.7+ to 1.8. Now it works. |
installing java8 (1.8) worked for me as well. Didn't have to worry about permission issue either (after approving it once--security wise-- it worked without having to disable gatekeeper). There may be another way to edit the Info.plist to allow it run under java9+... see my own comment on two different ways I got jd-gui working. These should work for getting jarzilla running, too. For now I'm sticking with the java8 install, which did fix my jarzilla launch issue. |
I'm experiencing issues launching Jarzilla on a clean install of macOS High Sierra (10.13.2). If I launch Jarzilla directly I get this error: The application "Jarzilla" can't be opened. If I try to open a jar file with it, nothing happens - no error and the app is not running per the Activity Monitor. Is there any trick to getting it to work?
I've tried running with 8u152-zulu, 8u151-oracle, 9.0.1-zulu and 9.0.1-oracle. All installed with SDKMAN.
I've checked the Console app and don't see any informative log messages. Are log messages written somewhere else?
The text was updated successfully, but these errors were encountered: