mirror of
https://github.com/aluxnimm/outlookcaldavsynchronizer.git
synced 2026-04-25 19:15:48 +03:00
[GH-ISSUE #386] Null reference exception at DDay.iCal.iCalTimeZoneInfo #371
Labels
No labels
1.0
1.0
1.0
2.0
Feature
Feature request
Google
Google Calendar
async
attachement
auto-migrated
auto-migrated
auto-migrated
bug
critical
enhancement
help wanted
implemented
pull-request
solved
solved
sourceforge
sourceforge
sourceforge
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/outlookcaldavsynchronizer#371
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @JGKle on GitHub (Apr 3, 2023).
Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/386
Using 4.4.0, for every sync, I'm getting the following exception:
Here's the ics:
Looks like this one, from back in 2016: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/107
@aluxnimm commented on GitHub (Apr 4, 2023):
Well our icalendar libraries has issues with exotic timezone definitions in VTIMEZONE, you just need to delete and recreate that appointment with a standard windows timezone definition for that location for example and it should go away.
@JGKle commented on GitHub (Apr 4, 2023):
If this is a known/recurring issue that won't be fixed, seems like it should at least have a clear user-facing message to that effect. It took me awhile just to notice that it was consistently failing, and then to realize that it was always the same item. Also note that I didn't explicitly choose the timezone for the reminder - I was simply traveling, and that was the default thta Outlook selected, due to Windows being on that timezone. A simple pop-up warning like "You have a calendar item that is failing to sync due to its timezone. Please delete this item & recreate with a different timezone" would no doubt save users a lot of time & confusion.