Building my first app and I’m having issues with the date-picker in app forms. Calendar renders nicely for example:
However, when I click on a day, for example here I clicked on Tuesday 8th
The correspoding field is always populated one day earlier - for example in this case April 7th.
Looking for ideas as this really makes it unusaeble. Anyone encountered this behavior?
Hi @valsoar1, I am trying to reproduce this issue but I’m not able to on my side.
What browser are you using? Are you able to send me a link to the published app so I can check this myself?
I’m using Edge on Windows 11, but I get the same result when I bring up the app on an iPad so I don’t beleieve its a browser specific issue.
Hey @valsoar1, could you also let us know your time zone?
I am in US/Eastern. That said I I will add that I am 5 hours behind GMT/Zulu, the date does not jump forward to GMT, it goes back one day. It also does so whether within 5 hours of midnight or greater than 5 hours from midnight.
Thank you both for looking at this.
Thank you @valsoar1. We have confirmed this is a bug. You can track the fix here: Date Localization Bug in Datepicker (#3566) · Issues · Baserow / baserow · GitLab 
Thank you for the update. I’ll watch for the fix.
Hopefully it can be fixed soon. The function of selecting the date and time in an application is unusable for the end user with this bug. What is selected in the calendar is different from what is actually selected for the database and causes confusion in every way.
Update: the problem is now inside the tables 
. I’m attaching a video.
Hi @khalil.io,
We’re sorry for the inconvenience. We recently had to upgrade the datepicker component and expected it to be a drop-in replacement, but unfortunately it wasn’t.
Could you let us know which timezone you’re in and which locale you’re using? We’ve noticed some mismatches between our locale codes and the ones used by the new datepicker, and I’m wondering if your issue might be related to that. We’re working on a fix as quickly as possible.
Hey @khalil.io, I just wanted to let you know that we’ve deployed a fix for this problem to baserow.io.
Hello @bram and @davide. Sorry I didn’t reply earlier. The time zone I used for the test was UTC‑5. I confirm that the error has been completely resolved 
. Thank you very much to the entire Baserow team! I’ll continue testing over the next few hours and will let you know if anything comes up, up to 24 hours after the initial report.
