You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
EventEvaluator and RecurrencePatternEvaluator seem to handle DTSTART and UNTIL's timezones incorrectly. It seems, that
RecurrencePatternEvaluator doesn't consider the time zone of the start value passed into RecurrencePatternEvaluator.Evaluate or CalendarEvent.GetOccurrences and
UNTIL must be specified as UTC (in most cases) according to RFC5545, but is treated as it would have the same time zone as DTSTART.
The following two test cases reproduce the problem (Europe/Vienna has offset UTC+2 in June 2018):
Not sure I understand the connection to #574. I think this issue a different one and we should reopen it. Probably related to #197, but that's to be shown.
EventEvaluator
andRecurrencePatternEvaluator
seem to handleDTSTART
andUNTIL
's timezones incorrectly. It seems, thatRecurrencePatternEvaluator
doesn't consider the time zone of the start value passed intoRecurrencePatternEvaluator.Evaluate
orCalendarEvent.GetOccurrences
andUNTIL
must be specified as UTC (in most cases) according to RFC5545, but is treated as it would have the same time zone asDTSTART
.The following two test cases reproduce the problem (Europe/Vienna has offset UTC+2 in June 2018):
(The problem was observed on a device running in the Europe/Vienna timezone. Not sure, whether this has any relevance to the outcome.)
[Edit]: Might be related to #197
The text was updated successfully, but these errors were encountered: