| Summary | Weekly by day recurring event ICS export issue with timezone |
| Queue | Kronolith |
| Queue Version | 4.1.4 |
| Type | Bug |
| State | Duplicate |
| Priority | 2. Medium |
| Owners | mrubinsk (at) horde (dot) org |
| Requester | horde (at) gavintech (dot) com |
| Created | 01/03/2014 (4201 days ago) |
| Due | |
| Updated | 03/25/2014 (4120 days ago) |
| Assigned | 01/23/2014 (4181 days ago) |
| Resolved | 01/23/2014 (4181 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
Bug: 12773Bug: 11339as well.Kronolith version (4.1.5) against Horde 5.1.6 and still have the issue.
I also attempted creating a brand new recurring event starting January
1, 2014 from 6:30 pm to 9:30 pm PDT in case the event being created in
an old Kronolith/Horde version was causing the issue. No improvement
was noted.
Here's the latest event:
BEGIN:VEVENT
DTSTART:20140107T023000Z
DTEND:20140107T053001Z
DTSTAMP:20140324T200110Z
UID:20140324125707.OOKWm5rRVOTV4KLAz_mq_A3@servername
CREATED:20140324T195707Z
LAST-MODIFIED:20140324T195707Z
SUMMARY:description
CLASS:PUBLIC
STATUS:CONFIRMED
TRANSP:OPAQUE
RRULE:FREQ=WEEKLY;INTERVAL=1;BYDAY=MO
END:VEVENT
No timezones are provided, and the event jumps to the day before after
the first occurrence.
State ⇒ Duplicate
Bug: 11339as well.State ⇒ Feedback
output with a valid vTIMEZONE object and the correct DTSTART/DTEND
values.
State ⇒ Assigned
Assigned to Michael Rubinsky
creates events on both sides of a DST transition.
isn't. That wasn't correct. The event was created in DST (UTC -7)
several years ago.
The actual behaviour I'm seeing is:
* During DST, the day is 1 day behind and the time is correct (6:30 pm)
* When DST is not in effect, the day is 1 behind and the hour is 1
behind as well (5:30 pm)
I have confirmed this behaviour in IOS 7, Lightning, and Google Calendar.
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ Weekly by day recurring event ICS export issue with timezone
Queue ⇒ Kronolith
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
BEGIN:VEVENT
DTSTART:20090915T013000Z
DTEND:20090915T043001Z
DTSTAMP:20140103T033921Z
UID:20090913191940.14556mns5e2c5n28@(myserver)
CREATED:20110501T223030Z
LAST-MODIFIED:20110501T223030Z
SUMMARY:(some event)
CLASS:PUBLIC
STATUS:CONFIRMED
TRANSP:OPAQUE
RRULE:FREQ=WEEKLY;INTERVAL=1;BYDAY=MO
EXDATE;TZID=America/Vancouver:20091117T023000Z
END:VEVENT
We are UTC -8 (UTC -7 during DST when the event was created) here.
The event is Mondays at 6:30 pm, or UTC 1:30 am on Tuesday.
Since you are exporting the date in UTC format, programs I'm importing
the event into expect the "RRULE" recur on day to be the UTC day as
well. So, it should be Tuesday rather than Monday for this event,
because the event happens on Tuesday UTC rather than Monday UTC.
I have confirmed that even though Horde displays this recurring event
on Mondays, both Thunderbird/Lightning, IOS 7, and Google Calendar
display this event on Sundays. They both get the time right, but the
day is off by one.
Recurring events that happen on the same day UTC and UTC -8 appear on
the correct day in these applications, so it's just this weird case
where the recurring event occurs on a different day UTC vs. UTC -8
(ie: events after 4:00 pm).