Unable to Open/Import module on MAC

[stricklandmw]

After recent Max OS upgrade I am not able Open or Import a module after launching VASSAL. Just seeing a gray window with the 'To start playing ....' message.

Here's snippet from the logs....
2019-06-29 16:27:38,499 [0-main] INFO VASSAL.launch.StartUp - Starting
2019-06-29 16:27:38,504 [0-main] INFO VASSAL.launch.StartUp - OS Mac OS X 10.15
2019-06-29 16:27:38,505 [0-main] INFO VASSAL.launch.StartUp - Java version 1.8.0_111
2019-06-29 16:27:38,505 [0-main] INFO VASSAL.launch.StartUp - VASSAL version 3.2.17
2019-06-29 16:27:38,992 [0-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManager - Manager

[Starlock]

Same problem here.

[JoelCFC25]

So after launching VASSAL, when you go to File -> Open module....what happens? Nothing? And no error messages generated in the log when you attempt that?

[Starlock]

That's correct. Nothing happens. No error messages in the log. The screenshot that I attached to this shows the log after I clicked "Open Module." Nothing in the log changed from before I clicked "Open Module."

[stricklandmw]

I am able to click New Module with window coming up. Issue appears to be related to Open/Import. No errors are reported in the log - window simply doesn't open.

[Starlock]

FYI: I updated to macOS Catalina Beta 2, and now Vassal just crashes on opening.

[Starlock]

Here's the error:

2019-07-12 09:34:47,675 [0-main] INFO VASSAL.launch.StartUp - Starting
2019-07-12 09:34:47,677 [0-main] INFO VASSAL.launch.StartUp - OS Mac OS X 10.15
2019-07-12 09:34:47,678 [0-main] INFO VASSAL.launch.StartUp - Java version 9.0.4
2019-07-12 09:34:47,678 [0-main] INFO VASSAL.launch.StartUp - VASSAL version 3.2.17
2019-07-12 09:34:48,049 [0-main] ERROR VASSAL.tools.ErrorDialog -
java.lang.NoSuchMethodError: com.apple.eawt.Application.addApplicationListener(Lcom/apple/eawt/ApplicationListener;)V
at VASSAL.launch.ModuleManagerMacOSXStartUp.setupApplicationListeners(ModuleManagerMacOSXStartUp.java:36) ~[Vengine.jar:na]
at VASSAL.launch.ModuleManagerMacOSXStartUp.initSystemProperties(ModuleManagerMacOSXStartUp.java:31) ~[Vengine.jar:na]
at VASSAL.launch.ModuleManager.<init>(ModuleManager.java:280) ~[Vengine.jar:na]
at VASSAL.launch.ModuleManager.main(ModuleManager.java:183) ~[Vengine.jar:na]

[JoelCFC25]

I'm still on OS X 10.14 and Java 8, so I can't offer any directly relevant personal experience, but there is a thread about difficulties with Java 9: viewtopic.php?f=3&t=10714

Obviously that doesn't address the initial problem, which was occurring while you had Java 8 running.

[imikem]

I am also having an issue with Vassal now refusing to open .vmod files.

macOS Mojave v10.14.6
MBP Pro 15", 2017
2.8GHz i7
16GB RAM

[JoelCFC25]

Version of Java is going to be key information.

[imikem]

I should circle back and answer my own posted issue in case others run into it. What was happening to me was the directory where my .vsav files are got moved to cloud storage and Vassal could not open the files via the link that iCloud left behind.