<@UH7J3DVPA> Hmm.. that's weird. Can you send me t...
# tornadofx
e
@Stephane M Hmm.. that's weird. Can you send me the executable you created, or at least the modified launcher jar with the manifest in it so I can check what's going on?
s
sent you via PM
e
Thanks. The update dialog will appear every time, but as you can see, it only verifies, and doesn't re-download the files. So it seems the issue here is with what's new. I've never used that myself (and I didn't write it), so I'll have to look into what it's doing to determine if it should show the dialog.
s
yes it doesn't re-download the file. My guess is that the "updating" screen is actually at fault here. It shouldn't show at all, only the circle screen. That was the behaviour from a past version of yours on Youtube
e
That would probably mean that the issue is in AbstractLauncher.syncFiles
That would mean that one or more of these checks fail:
!Files.exists(path) || Files.size(path) != size || checksum(path) != checksum;
So most probably either the file size is reported differently between the local file system and what's in the manifest, or that the checksum doesn't generate the same value
s
You're probably right, but I've reached the boundary of my knowledge here 🙂
e
I will have a look 🙂
❤️ 1
It seems the issue is that the checksum for conduktor-1.0-SNAPSHOT.jar is changed between the previously downloaded version compared to what's written in the remote manifest. Trying to figure it out now.
👍 1
Yeah, that's the issue. The checksum written in app.xml is not correct for conduktor-1.0-SNAPSHOT.jar. You can verify by changing the checksum for that file in the manifest to 1706656308 and see if the dialog dissappears
If it does, we need to figure out why the checksum is wrong. One reason could be that the snapshot jar was uploaded and a new app.xml was not.
👍 1
s
so do I change the "online" app.xml checksum?
e
Yeah, to see if we're on the right track
s
@edvin I'm checking but the checksum for that file in the online app.xml is already 1706656308
e
Ah, so what's happening is actually that the new manifest is not consulted. Have some things to do now, will look at it asap!
s
Thanks 🙂