nextcloud / nextcloud/calendar
Recurring event shows twice with one day offset
Open
Nobody has claimed this yet.
1. to develop
bug
hotspot: recurring events
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 332
- Avg merge
- 16h 13m
- Merged PRs (30d)
- 137
Description
Steps to reproduce
- Import
BEGIN:VCALENDAR
VERSION:2.0
CALSCALE:GREGORIAN
PRODID:-//IDN nextcloud.com//Calendar app 4.6.5//EN
BEGIN:VEVENT
CREATED:20240221T100133Z
DTSTAMP:20240221T101146Z
LAST-MODIFIED:20240221T101146Z
SEQUENCE:6
UID:0e81-46fc-8c9a-44a4a8ee6093-c68a5083
DTSTART;VALUE=DATE:20240104
DTEND;VALUE=DATE:20240106
STATUS:CONFIRMED
SUMMARY:Test event
RRULE:FREQ=WEEKLY;BYDAY=TH,FR
EXDATE;VALUE=DATE:20240105
END:VEVENT
END:VCALENDAR
### Expected behavior
Event shows Thu+Fr
### Actual behaviour
Event shows Thu+Fr and Fr+Sa

### Calendar app version
4.6
### CalDAV-clients used
_No response_
### Browser
_No response_
### Client operating system
_No response_
### Server operating system
_No response_
### Web server
None
### Database engine version
None
### PHP engine version
None
### Nextcloud version
_No response_
### Updated from an older installed version or fresh install
None
### List of activated apps
_No response_
### Nextcloud configuration
_No response_
### Web server error log
_No response_
### Log file
_No response_
### Browser log
_No response_
### Additional info
_No response_
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue by importing the provided ICS data into Calendar app 4.6, then trace recurrence expansion and EXDATE handling from the import path. No file or test is named in the report; done means the event appears only as Thu+Fri, without the extra Fri+Sat occurrence, with regression coverage for this recurrence case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100