What’s The Bug? When creating an object in a set while in your ‘home timezone,’ everything works as expected if you use the current date. However, after changing time zones, Anytype displays the events as occurring one day earlier, even when there’s no actual day difference. How To Reproduce It Cr…

This report has been added to our issue tracker and received by the Development Team.

not sure if this is the right place to put this but… I imported a database from Notion to Anytype. I had it in a calendar view in Notion and when I imported it Anytype, everything was 1 day off. Maybe this has something to do with the import process from Notion to Anype? I thought they were look…

[image] Jason_22: would this be the same bug? It would be a different bug for sure, especially since this is only an Android bug.

okay. so do i need to start a new bug report for this one? i did not see another one. i did this on my Mac studio between Notion.so and Anytype App.

[image] Jason_22: so do i need to start a new bug report for this one? Yes, please a submit a separate bug.

I just created it now. [image] Notion Import date errors Bug Reports What’s The Bug? when I export from Notion and import into Anytype, I’m getting errors with the dates. The date I put in my Notion database is one day off when it gets imported into Anytype as…

I also have this issue. In the Windows App you can show the time of the due date - it’s always 0:00. If you move the timezone by one hour, it’s 23:00 the day before - so the due date changes. In Android I don’t see an opportunity to deal with time - so a quick workaround would be to have 12:00 inst…

Thanks for reporting this. Could you please confirm which device you are using when this happens (Android, Windows, or another platform)? Also, please share at least your Anytype app version, and if possible: • OS version • the exact steps you followed before the dates shifted Regarding your qu…

I see the same behavior in Windows 0.54.5 and Android 0.45.7. The app behaves logically so I don’t think it’s a bug. These are the steps: create a task add a due date switch the time zone to -1 (Western) Check the due date (expected: same than in step 2, observed: one day before) It’s unfortunat…

Thanks for the detailed explanation, this makes sense. You’re right that the behavior is technically logical: if a date is stored as 00:00, moving one hour back shifts it to 23:00 of the previous day, which then appears as one day earlier. At the moment, there is no way to change the default time…

TimeZone Switching leads to -1 day difference in date fields

Bug Reports

Jason_22 February 3, 2025, 7:06am 8

I just created it now.