jpickup
Workouts are shifted one day earlier
Hi it's me again 🙇
So everything is working great ! I got my workouts and my schedule on my watch but... All the trainings are shifted by one day ! We are currently on the 11th April 2025 (I'm in France) and my training start on the 12th April (as showed on the .xlsx file linked) but my watch pushes me the tomorrow workout (marked as today's workout) and when I watch the schedule on my watch, I can see the right series of workouts, but every one of them one day earlier !
Do you have a hint on how to solve this ?
I have seen this before and thought it was fixed, but clearly it isn't. My best guess is that I've got a bug related to timezones and somewhere I must be using the UTC date instead of the local date. I will have a look this weekend.
Quick question: are you running Windows or Mac? I've just moved to a new M4 Mac and that could well cause me trouble when trying to create Windows executables, which was possible on my old Intel Mac. If you are on a Mac then that'll be easier for me to get a new version to you. Or, even better, if you are able to run from the source code, e.g. in IntelliJ, then I can let you know when I've made an update and you can try it immediately rather than waiting for me to build the executable bundles.
Unfortunately I am on Windows.
I can just shift my dates on my excel for one day and that will do the trick ! I dont want to go through additional work for this if it is a rare thing !
Yeah but thats actually a quick win for me and it is easy to do on excel !
I've just had a look and the reason this was so familiar is that I fixed the issue 8 months ago but, crucially, I didn't create a new version of the Windows installer. I'll see if I can do this on a friend's PC as without the Intel Mac I don't think this will be too easy now (I do have a Windows VM on this machine but it's the ARM version so I have doubt that the output will work on Intel).
Unless of course you are able to compile the app yourself? If you've got the Java JDK installed plus Maven then you should be able to run the build. Please let me know if this is an option - thanks.
Here's how your schedule looks on my watch with the newer version:
I know I attempted to compile it, and it was a struggle for a bit. Not all things are in the repo that you need. So just be aware of that. Happy to attempt to compile it.
I've also started to look into putting this into Docker in my free time
On Fri, Apr 11, 2025, 11:23 John Pickup @.***> wrote:
I've just had a look and the reason this was so familiar is that I fixed the issue 8 months ago but, crucially, I didn't create a new version of the Windows installer. I'll see if I can do this on a friend's PC as without the Intel Mac I don't think this will be too easy now (I do have a Windows VM on this machine but it's the ARM version so I have doubt that the output will work on Intel).
Unless of course you are able to compile the app yourself? I've you've got the Java JDK installed plus Maven then you should be able to run the build. Please let me know if this is an option - thanks.
— Reply to this email directly, view it on GitHub https://github.com/jpickup/GarminTools/issues/15#issuecomment-2797549686, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAV2IWDRCU4V7T4GGS4SN4D2Y73CBAVCNFSM6AAAAAB26KGKEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJXGU2DSNRYGY . You are receiving this because you are subscribed to this thread.Message ID: @.***> jpickup left a comment (jpickup/GarminTools#15) https://github.com/jpickup/GarminTools/issues/15#issuecomment-2797549686
I've just had a look and the reason this was so familiar is that I fixed the issue 8 months ago but, crucially, I didn't create a new version of the Windows installer. I'll see if I can do this on a friend's PC as without the Intel Mac I don't think this will be too easy now (I do have a Windows VM on this machine but it's the ARM version so I have doubt that the output will work on Intel).
Unless of course you are able to compile the app yourself? I've you've got the Java JDK installed plus Maven then you should be able to run the build. Please let me know if this is an option - thanks.
— Reply to this email directly, view it on GitHub https://github.com/jpickup/GarminTools/issues/15#issuecomment-2797549686, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAV2IWDRCU4V7T4GGS4SN4D2Y73CBAVCNFSM6AAAAAB26KGKEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJXGU2DSNRYGY . You are receiving this because you are subscribed to this thread.Message ID: @.***>
I think I have a working Windows installation now. Unfortunately I have failed to get the original MSI installer working as I can't seem to find compatible versions of Java + Wix + .NET. The best I've managed is to create a ZIP file that inside it has the EXE plus required Java runtime.
@florianleux please can you download the ZIP, extract it somewhere local and run GarminTools.exe. Please let me know if this works. Not quite as nice as a proper installer but the best I can do right now.
@surbeym things I had to install and problems I faced when trying to get this working on a fresh Windows machine:
- a JDK - anything >= 17 should do. I tried 17, 23 & 24
- Maven
- Set the JAVA_HOME env variable to the JDK installation
- .NET sdk (required for WIX)
- wix (installed via dotnet.exe tool install --global --version 5.0.0) Steps 4 & 5 are new, possibly related to using a newer version of Windows versus what I last used a couple of years ago.
At this point the maven build works up until the final jpackage step, which fails with error 144. From what I can tell jpackage only works with wix v3 but JDK24 is meant to work with v4 & v5 but fails. I see an open issue logged (https://bugs.java.com/bugdatabase/view_bug?bug_id=8347024) so I'm not the only one with this issue!
- The solution to the above was to change the installer_type in build_app_windows.bat to app-image and then remove all the --win-* options from the jpackage command. The end result is a directory under the app module target/installer/GarminTools/ that contains the EXE plus Java runtime and the app's jars.