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
Currently, the first time the app is run, MonkeyPath tries to find the location of the JVM on the user's machine, and then writes the location to a file. The issue is that because the location is only known after the first run, the application has to be opened, closed, and then reopened for it to start working after installation. So far this only seems to be an issue with windows. On mac, the application works the first time.
From what I understand, when the installer runs on windows, it runs the application for the first time with a certain flag set that you can detect in the code. So basically, you need to detect that tag, run the bit of code that finds the JVM, and then kill the program. If that flag isn't present, then the program can run normally.
Currently, the first time the app is run, MonkeyPath tries to find the location of the JVM on the user's machine, and then writes the location to a file. The issue is that because the location is only known after the first run, the application has to be opened, closed, and then reopened for it to start working after installation. So far this only seems to be an issue with windows. On mac, the application works the first time.
From what I understand, when the installer runs on windows, it runs the application for the first time with a certain flag set that you can detect in the code. So basically, you need to detect that tag, run the bit of code that finds the JVM, and then kill the program. If that flag isn't present, then the program can run normally.
See this for more: https://github.com/electron/windows-installer#handling-squirrel-events
The text was updated successfully, but these errors were encountered: