"Couldn't parse iCalendar source" on validated iCal source
-
Hi,
I get an error for a validated calendar source “Couldn’t parse iCalendar source” on my Android CyanogenMod phone.
I don’t know how to proceed to solve the issue.0_1538559218669_userid-157.ics
I access this file via an URL and I can download it via a browser. Access to the file should be fine.
Best,
Saren.T
Grüße aus Wien
-
Hello,
If you use an iCalendar validator like this: https://ical-validator.herokuapp.com/validate/
You can see the message:Parser error at line 31: Cannot set timezone for UTC properties
Line 31:
DTSTAMP;TZID=TZID_PMS-ST:20180713T090000See https://tools.ietf.org/html/rfc5545#section-3.8.7.2 DTSTAMP:
“The value MUST be specified in the UTC time format.”
Does it work when you fix the DTSTAMP so that it’s in UTC format?
-
@rfc2822 said in "Couldn't parse iCalendar source" on validated iCal source:
I see. I used another online tool, which seems to be more tolerant. The file is from a server, which I am not administering. I will contact the administrator.
-
@saren-t https://icalendar.org/validator.html doesn’t find this problem. I have just reported that now.
-
@rfc2822 Yes, I used that one. But ietf seems to be clear on this. But also Lightning can read the same source without any problem.
-
@saren-t said in "Couldn't parse iCalendar source" on validated iCal source:
But also Lightning can read the same source without any problem.
Yes, Lightning does not use the ical4j library, which is quite strict about this. I wonder what the original intention of the standard is, but I guess its purpose is that servers can detect the timestamp of entries without having to calculate time zones.
