search

edvin / fxlauncher

Auto updating launcher for JavaFX Applications
Apache License 2.0
713 stars 110 forks source link

fxLauncher in Windows #83

Closed albertoclarit closed 7 years ago

albertoclarit commented 7 years ago

Hi Edvin,

fxLauncher will update even though theres no new updates since the last run. See https://youtu.be/nHkkD-UgFbE

Any mistakes i made? The demo native installer works just fine.

Thanks

mordechaim commented 7 years ago

Honestly, I'm still familiarizing with the project, but could you be missing the cache dir manifest attribute? Might not be the problem, just trying.

FWIW post your manifest for better observation.

albertoclarit commented 7 years ago

Im using a native installer...I though the cache-dir option is not needed at this point ... anyways i will try that... hang on

edvin commented 7 years ago

It would be interesting to se the console output for the application. Can you start it from the command line and paste the log output? It could be related to the cache dir somehow, but I'd need the log to be sure.

albertoclarit commented 7 years ago

Hi guys... my App manifest is here http://cm.hisd3.com/app.xml

Im running the native installers... theres no output if i run them in command line...

Though I observe this behavior. If I run ./gradlew deployApp and ./gradlew generateNativeInstaller on OSX, the App will behave as expected.

But when I make the gradlew generateNativeInstaller on windows (since i already uploaded in the osx) ... the windows native bundle is always downloading.

I check their app.xml and they differ on <Application ts="???" ...> line.

Does that matter?

edvin commented 7 years ago

That shouldn't matter, since ts is just the timestamp the manifest was created. I could add debugging support to the launcher so we can see what's going on. My problem is time, just don't have enough of it at the moment :(

albertoclarit commented 7 years ago

I was able to workaround the issue...

I notice that if I have generated the native installer after i uploaded the dependencies... it will result into a loop which the native installer always downloads the dependencies

Workaround was to generate native installers first then deploy the app to the servers.

Thanks ...