Time zone issues with CalDAV subscribed calendars
maxens-git opened this issue · 8 comments
The (???) part is displayed for meetings when the event timezone is different from your system, but the time you see is actually your local time.
This is just so you know that whoever created the meeting is in a different timezone than yours.
For example, when I go to Brazil I usually see (GMT-3), but the event is displayed in local time.
There is a two hour time lag between Apple's calendar app and Calendr.
it was not activated, but that does not change anything, I specify that the events were created in the same time zone as where I am
I found a solution, I am subscribed to an ics calendar, and I am connected to a caldav account to have the events on my mac, but if I subscribe directly from the calendar application on macOS, this is no longer a problem
I explicitly disabled timezone for subscribed calendars on version v1.9.2
.
That's because I had the same setup as you. I had a subscribed calendar on Google and was synching it with my mac, but I was getting the wrong timezone.
Google probably does the conversion before reaching Apple's calendar, but still returns UTC, so Calendr was doing the conversion 2x. It's pretty unreliable. There are tons of issues around regarding subscribed calendars.
I think I found the issue:
- I was only ignoring the timezone for
"subscribed"
calendars, but you were using a subscription fromCalDAV
, which is called"delegated"
calendar. - This type of calendar returns
false
forisSubscribed
in the code. I have to also check forisDelegate
, which is only available on macOS 13. 🫠
I've made some changes to check that if we can, feel free to try it out with your previously setup and please, tell me if it worked. 🙏🏻
Thanks, I will test this tonight