I did some more testing and applied this patch https://github.com/owncloud/contacts/pull/1068 to my owncloud. This fixes the issue for me. I have done it manually since there is no official update which fixes the issue. If there are others who can test this on their installation maybe a few more comments on github help to speed up an official fix that non-technical people can profit from it as well.
"Couldn't parse iCalendar source" on validated iCal source
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.
I access this file via an URL and I can download it via a browser. Access to the file should be fine.
Grüße aus Wien
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
See https://tools.ietf.org/html/rfc5545#section-126.96.36.199 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?
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.
@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.
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.