mirror of
https://github.com/aluxnimm/outlookcaldavsynchronizer.git
synced 2026-04-26 11:35:47 +03:00
[GH-ISSUE #290] iCloud calendar with address - error when parsed #747
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#747
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 @lukakrevs on GitHub (Oct 13, 2020).
Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/290
error.txt
When the event in attachement is parrsed there is an error line 17:1: expecting "END", found '1210'
I think this is due to the value in X-APPLE-STRUCTURED-LOCATION
@aluxnimm commented on GitHub (Oct 14, 2020):
I guess the line folding is not correct, since the 1210 line is not a property.
@lukakrevs commented on GitHub (Nov 3, 2020):
The content should probably look like this:
X-APPLE-STRUCTURED-LOCATION;VALUE=URI;X-ADDRESS="Ulica Jožeta Jame 12\n12 10 Ljubljana - Šentvid\nSlovenia";X-APPLE-ABUID=Servis Bizilj's Work;X-TITLE="Ulica Jožeta Jame 12\n 1210 Ljubljana - Šentvid\nSlovenia"Is it possible that this entry's would be parsed anyway ignoring bad properties at least as an option?
@daveewall commented on GitHub (Apr 9, 2021):
I second this.
Unfortunately, this issue pops up for multiple events in my calendar, and whenever it happens, it creates empty calendar events on the date/time of sync that need to be deleted. It's a showstopper for me, because it causes bad data in the calendar, and doesn't get the events on the calendar, even without the failing location, which would have been acceptable for my use case, at least.
Below are some examples from my calendar that are failing. I think it's a simple newline that's killing them.
Hoping this can be resolved in the next release so I can continue using this. :-)
@MrPinrel commented on GitHub (Jun 15, 2021):
I am having this issue as well. Anytime I create a new calendar event on an iOS device and use Apple to help me enter the exact location (using the address of one of my contacts, or an address from Apple Maps), it gets saved as a X-APPLE-STRUCTURED-LOCATION property that somehow trips up caldavsynchronizer. It would be great to see this fixed in the next release.