Appsheet DateTime not accurate after saving in Postgres

[Rain-Kun]

Hello, I'm having a bugs and it started on August 31, 2024 at around 8AM here in the Philippines, when I inputted date and time in the field using AppSheet form, after saving it to database which is PostgreSQL, the actual date and time always incremented by 8 hours. I cant fix the bugs and prior August 31 all dates are accurate. Thank you for your assistance on this matter.

[WillowMobileSys]

Have you implemented or changed date implementations and used any UTC functions?  The increment by 8 hours is synonymous with UTC offset for the Philippines.

You may want to also check the PostgreSQL database to make sure there isn't some auto-translate of the Date Time happening there.

If these all check out then you will need to contact AppSheet support for additional help!

[pumpkin_link]

I'm having the same exact issue that started around the same time (somewhere between August 26 and September 3).

I've been discussing with Appsheet support via email for weeks, I even made a video capture of the bug and showing my Postgres database config and all they do is keep repeating generic phrases from the documentation and basically implying that my database configuration is wrong.

The worst part is that the user-selectable Date fields get offset a full day back when persisting to the DB (I live in a minus 3 timezone).

[AleksiAlkio]

Hi, may I ask what is your case ID?

[pumpkin_link]

Hi, I guess it is this number [3-6759000037044] .

[AleksiAlkio]

Are you using a cloud database or on prem with Dreamfactory?

[pumpkin_link]

I'm using a cloud database hosted in gcp cloud sql

[AleksiAlkio]

Thanks

[Steve]

Attn @AleksiAlkio 

[AleksiAlkio]

This behavior change is coming from the third party library update that handles the date and time differently than earlier. Meaning.. the change itself is not coming from AppSheet. You can read more from here.. npgsql.org/doc/release-notes/6.0.html#major-changes-to-timestamp-mapping

[pumpkin_link]

Thank you for the reply but... all timestamp columns (including timestampTZ) are still getting double offset and "date" columns are completely broken, getting truncated a full day back/forward.

I get it that appsheet's dotnet backend uses that library but it's not like the dependency version just changed by itself, from my point of view that behavior change is clearly a regression bug on the appsheet platform. Don't get me wrong but am I supposed to expect a bugfix or was that reply a "works as intended" response? Because if that's the case, I guess I'll be forced to migrate to MySql or something

[AleksiAlkio]

This is something devs are investigating.. like how to fix the issue, even the change itself is coming outside of AppSheet.