You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
No idea if it is related to issue #22 on Mac, but I spent half an hour today trying to figure out why ISO Viewer didn't work on my PC at work (Win10 Pro 64b, Intel Core i7), to no avail.
I now just tested on my home PC (Win10 Pro 64b, Intel Core i9) and got the same result, which is... nothing.
The app installs fine, it can be found in the start menu, but upon execution, it just does nothing. No window pops up, no error message, nothing. I also tried running it from the command line, but nothing gets printed, it's like the app was never run.
I finally downloaded the zip for v2.0.2 and it works like a champ, so I guess the jpackager needs some fine tuning...
Keep on the good work,
Vicne
The text was updated successfully, but these errors were encountered:
Issue with packaging. Looking at the error output:
Error occurred during initialization of boot layer
java.lang.module.FindException: Two versions of module isoviewer found in C:\Program Files\ISO Viewer\app (isoviewer-2.0.3.jar and isoviewer-2.0.2-SNAPSHOT.jar)
if I manually delete the SNAPSHOT.jar then I can run the app fine.
Hi,
No idea if it is related to issue #22 on Mac, but I spent half an hour today trying to figure out why ISO Viewer didn't work on my PC at work (Win10 Pro 64b, Intel Core i7), to no avail.
I now just tested on my home PC (Win10 Pro 64b, Intel Core i9) and got the same result, which is... nothing.
The app installs fine, it can be found in the start menu, but upon execution, it just does nothing. No window pops up, no error message, nothing. I also tried running it from the command line, but nothing gets printed, it's like the app was never run.
I finally downloaded the zip for v2.0.2 and it works like a champ, so I guess the jpackager needs some fine tuning...
Keep on the good work,
Vicne
The text was updated successfully, but these errors were encountered: