Open lukakrevs opened 3 years ago
I guess the line folding is not correct, since the 1210 line is not a property.
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?
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. :-)
X-APPLE-STRUCTURED-LOCATION;VALUE=URI;X-APPLE-MAPKIT-HANDLE=CAES/gEI2TIa
EgkZbmUuFRxEQBFah/5kZ7hSwCJpCg1Vbml0ZWQgU3RhdGVzEgJVUxoMUGVubnN5bHZhbmlh
IgJQQSoFQnVja3MyB1lhcmRsZXk6BTE5MDY3UhBGbG9yYWwgVmFsZSBCbHZkWgM4MDhiFDgw
OCBGbG9yYWwgVmFsZSBCbHZkKhQ4MDggRmxvcmFsIFZhbGUgQmx2ZDIUODA4IEZsb3JhbCBW
YWxlIEJsdmQyEllhcmRsZXksIFBBICAxOTA2NzINVW5pdGVkIFN0YXRlczg5QABaJwolEhIJ
GW5lLhUcREARWof+ZGe4UsAY2TIg8Yer87Ht4rX0AZADAQ==;X-APPLE-RADIUS=11.52462
119003101;X-APPLE-REFERENCEFRAME=1;X-TITLE="Growing Smiles in Floral Val
e
808 Floral Vale Blvd, Yardley, PA 19067, United States":geo:40.219396\,
-74.881311
X-APPLE-STRUCTURED-LOCATION;VALUE=URI;X-APPLE-MAPKIT-HANDLE=CAESpwII2TIa
EgkCTHTxEmRCQBHjXeRUIQ9TwCKRAQoNVW5pdGVkIFN0YXRlcxICVVMaCFZpcmdpbmlhIgJW
QSoKQ2hlc2FwZWFrZTIKQ2hlc2FwZWFrZToFMjMzMjBCCkdyZWVuYnJpZXJSDkNyb3Nzd2F5
cyBCbHZkWgQxNTYyYhMxNTYyIENyb3Nzd2F5cyBCbHZkigEKV2FzaGluZ3RvbooBCkdyZWVu
YnJpZXIqEzE1NjIgQ3Jvc3N3YXlzIEJsdmQyEzE1NjIgQ3Jvc3N3YXlzIEJsdmQyFUNoZXNh
cGVha2UsIFZBICAyMzMyMDINVW5pdGVkIFN0YXRlczg5QABaJgokEhIJAkx08RJkQkAR413k
VCEPU8AY2TIgkaTguf6cyth0kAMB;X-APPLE-RADIUS=91.62338417421356;X-APPLE-RE
FERENCEFRAME=1;X-TITLE="1562 Crossways Blvd
Chesapeake, VA, United States":geo:36.781828\,-76.236409
X-APPLE-STRUCTURED-LOCATION;VALUE=URI;X-APPLE-MAPKIT-HANDLE=CAESgAII2TIa
EgmJ+ah10RNEQBEy5UNQtc1SwCJtCg1Vbml0ZWQgU3RhdGVzEgJVUxoMUGVubnN5bHZhbmlh
IgJQQSoKTW9udGdvbWVyeTIGQW1ibGVyOgUxOTAwMlIQUyBCZXRobGVoZW0gUGlrZVoDMTE2
YhQxMTYgUyBCZXRobGVoZW0gUGlrZSoUMTE2IFMgQmV0aGxlaGVtIFBpa2UyFDExNiBTIEJl
dGhsZWhlbSBQaWtlMhFBbWJsZXIsIFBBICAxOTAwMjINVW5pdGVkIFN0YXRlczg5QABaJgok
EhIJifmoddETREARMuVDULXNUsAY2TIgpOGO4fDbuoZ5kAMB;X-APPLE-RADIUS=32.22582
982883208;X-APPLE-REFERENCEFRAME=1;X-TITLE="116 S Bethlehem Pike
Ambler, PA, United States":geo:40.154830\,-75.214191
X-APPLE-STRUCTURED-LOCATION;VALUE=URI;X-APPLE-MAPKIT-HANDLE=CAESjQII2TIa
Egm1e6gjNhVEQBEcLPdd7MJSwCJxCg1Vbml0ZWQgU3RhdGVzEgJVUxoMUGVubnN5bHZhbmlh
IgJQQSoFQnVja3MyC1NvdXRoYW1wdG9uOgUxODk2NlISU2Vjb25kIFN0cmVldCBQaWtlWgMz
MTliFjMxOSBTZWNvbmQgU3RyZWV0IFBpa2UqFjMxOSBTZWNvbmQgU3RyZWV0IFBpa2UyFjMx
OSBTZWNvbmQgU3RyZWV0IFBpa2UyFlNvdXRoYW1wdG9uLCBQQSAgMTg5NjYyDVVuaXRlZCBT
dGF0ZXM4OUAAWiYKJBISCbV7qCM2FURAERws913swlLAGNkyINPdssWwhJjvSJADAQ==;X-A
PPLE-RADIUS=84.9591140913751;X-APPLE-REFERENCEFRAME=1;X-TITLE="Tri Count
y Eye Physicians & Surgeons
319 Second Street Pike, Southampton, PA 18966, United States":geo:40.16
5715\,-75.045677
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.
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