Weight tracker: Date selection
Steps to Reproduce
- Open the F-Droid App on GrapheneOS/Android
- Press + on the Weight tab
Expected results: The current date is automatically selected.
Actual results: The date of the latest entry is selected.
Can i fix this issue ?
I believe this is fixed already.
In the droid APP - its giving an error of wrong date format.
It populates with: MM/DD/YYYY but is expecting YYYY-MM-DD
This is with latest version installed as of today.
@pschilly the date in the ui is localized, but should be sent as Iso8601 to the server. Are you getting errors when submitting the form?
@pschilly the date in the ui is localized, but should be sent as Iso8601 to the server. Are you getting errors when submitting the form?
Yes thats correct. It won't let the form submit and save.
Could you post a screenshot? Both of these worked fine for me
I will yes... as soon as cloudflare stops being dead hah
Here it is - in the android app.
mhhh, are you perhaps using an older docker image? We did remove some time ago the constraint that you could only have one weight entry per day, so instead of the yyyy-mm-dd we now send a timestamp with time information, but that was some months ago
mhhh, are you perhaps using an older docker image? We did remove some time ago the constraint that you could only have one weight entry per day, so instead of the yyyy-mm-dd we now send a timestamp with time information, but that was some months ago
Ahhh... im using whayever one was in the proxmox community scripts.. ill double back and try the latest docker
ah those scripts! Those are using an older release (well, the last tagged one), you can safely use master, which is what we do as well. We might change how often we tag new releases in the future, but for now that's the solution :)
Hey, I just installed wger on proxmox with the helper script. It seems to be up to date, see the photo. But it stil says wrong date format. Can someone help me? Thank you
@SuperOldboy note that while you have the latest released version, it's still an old one. We'll be doing more "proper" releases for the backend in the future (the "official" deployment via docker compose simply uses "latest"), take a look at #2150 which we need to finish first. After updating the mobile app should work fine again