View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0005229 | SOGo | Web Calendar | public | 2020-12-01 07:48 | 2022-05-04 11:55 |
Reporter | aron33 | Assigned To | |||
Priority | high | Severity | major | Reproducibility | always |
Status | new | Resolution | open | ||
Platform | [Client] Apple | OS | Debian | OS Version | 10 |
Product Version | 5.0.1 | ||||
Summary | 0005229: IOS CalDav incorrect start time | ||||
Description | When creating an event in the calendar on iOS (14.2) or macOS (Big Sur 11.0.1) connected via CalDav to SoGo Web Calendar, this event appears with an incorrect start and end time, it shifts forward by 29 minutes.
The sogo_quick_appointment table contains the values c_startdate and c_enddate in UNIXTIME format, in which there is already an offset of 29 minutes:
Logs:
| ||||
Tags | No tags attached. | ||||
Hi. Same problem here. It is not a SOGo problem. It's a bug in apple CALDAV protocol. They uses an old python library which uses astronomical time for some timezones like Moscow. |
|
https://blog.ganssle.io/articles/2018/03/pytz-fastest-footgun.html https://stackoverflow.com/questions/62114498/python-timezone-problem-with-the-same-timezone |
|