DateTime is not converting to local time on real device about isar HOT 5 CLOSED

Maybe I'm not understanding the error properly, but this seems to be working as expected.
Isar saves dates as utc epoch microseconds, and reads them as utc epoch microseconds and then converts them to local.
I'm assuming your timezone is UTC-3?

from isar.

Talvez eu não esteja entendendo o erro corretamente, mas parece estar funcionando conforme o esperado. Isar salva datas como microssegundos da época UTC, lê-as como microssegundos da época UTC e depois as converte para locais. Presumo que seu fuso horário seja UTC-3.

Exactly, but look at the prints. The convert to local behavior does not occur on the real device, only on the emulator

from isar.

Talvez eu não esteja entendendo o erro corretamente, mas parece estar funcionando conforme o esperado. Isar salva datas como microssegundos da época UTC, lê-as como microssegundos da época UTC e depois as converte para locais. Presumo que seu fuso horário seja UTC-3.

Exactly, but look at the prints. The convert to local behavior does not occur on the real device, only on the emulator

The value that you are passing to isar is 2024-05-01T00:00:00.000Z, which is in UTC.
Isar then returns 2024-04-30T21:00:00.000, which is the exact same value as the input, but in your local time (UTC-3).

from isar.

Talvez eu não esteja entendendo o erro corretamente, mas parece estar funcionando conforme o esperado. Isar salva datas como microssegundos da época UTC, lê-as como microssegundos da época UTC e depois as converte para locais. Presumo que seu fuso horário seja UTC-3.

Exactly, but look at the prints. The convert to local behavior does not occur on the real device, only on the emulator

The value that you are passing to isar is 2024-05-01T00:00:00.000Z, which is in UTC. Isar then returns 2024-04-30T21:00:00.000, which is the exact same value as the input, but in your local time (UTC-3).

I think I structured the issue wrong... See, I sent 6 screenshots, the first 3 are from my real device, where isar removes -3 hours, making it a UTC date as expected, but when trying to get the entered value, it is not converting to the local time, which would be +3 hours.

Now, the other 3 prints are from the emulator, where ISAR removes -3 hours at the time of insertion and adds +3 hours at the time of obtaining the Date. In this example, I understand that it is the correct way.

Another important detail is that both devices are UTC-3, as we can see at the time of insertion, but the results are different.

from isar.

I found the problem, I was saving the data with DateTime.utc... I removed that and put the conventional DateTime.

For some reason this was causing inconsistency between devices.

from isar.