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
Describe the bug
When importing an ICS event, which has DTSTART on a thursday for example and RRULE BYDAY is set to wednesday, the event will repeat on thursdays.
To Reproduce
Steps to reproduce the behavior:
Such ICS entries can be created using Thunderbird for example and a few calendar apps and programs I tested by hand did not show this behavior. The following event can be used to replicate the issue:
HappyLer
changed the title
Events with RRULE BYDAY set to day are repeated on day of DTSTART #2225
Events with RRULE BYDAY set to day are repeated on day of DTSTART
Jan 22, 2024
Can you fix formatting of code snippet? You added ``` without the line break before :)
Also, this issue is valid, however I don't know if it will be done before adding the support for such case while creating events. Now, while creating recurring events, there is no way to set a different day for monthly occurrences.
Checklist
Describe the bug
When importing an ICS event, which has DTSTART on a thursday for example and RRULE BYDAY is set to wednesday, the event will repeat on thursdays.
To Reproduce
Steps to reproduce the behavior:
Such ICS entries can be created using Thunderbird for example and a few calendar apps and programs I tested by hand did not show this behavior. The following event can be used to replicate the issue:
Expected behavior
The repeated events should be placed where RRULE points to and not to the first day it happened.
Device info (please complete the following information):
Additional context
I think the issue lies in Parser.kt in line 178, where day is set to the day of the event start timestamp instead of the day from the RRULE. https://github.com/FossifyOrg/Calendar/blob/4363adce4b0d36d44b8fc4de2f87fcb5ba074ef2/app/src/main/kotlin/org/fossify/calendar/helpers/Parser.kt#L180C1-L180C57
The text was updated successfully, but these errors were encountered: