Sub-classes of UtcProperty (like CREATED, DTSTAMP, …) are not allowed to have localized DATE-TIME properties. If they have such lines the CalendarBuilder fails with "net.fortuna.ical4j.data.ParserException: Error at line XX:Cannot set timezone for UTC properties".
However, some popular calendar clients (1) generate such non-conform iCalendars. And it would be wonderful if the CalendarParser could be made more relaxed to just read them (e.g. convert the according values to UTC).
Or is there some other good workaround? (I did not find any solution in this forum or with gewgle).
(1) Users reported them, I didn't verify them: Mac iCal, Google Calendar.
Apologies for the delay in following up. I have added a card to the ical4j trello board to investigate supporting non-UTC values via Compatibility Hints:
If you could verify CUAs that have this issue (e.g. Outlook, Gooogle Calendar, etc.) that would really be appreciated.
Would there currently be a way to work around this issue ?
Log in to post a comment.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.