improperly set recurrence-id

[barkyq]

Checklist

• I can reproduce the bug with the latest version given here.
• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
• I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one bug.
• I have read and understood the contribution guidelines.

Affected app version

1.1.0

Affected Android/Custom ROM version

15

Affected device model

pixel 7

How did you install the app?

GitHub releases

Which calendar service or provider do you use, if any?

CalDAV server

Which sync adapter app do you use for calendar synchronization, if any?

DAVx5

Steps to reproduce the bug

1. Create a recurring event:

For instance, create a recurring event which starts on January 2nd at 10:00AM Paris Timezone. Correctly creates an event which is synced by DAVx5 to the CalDAV server:

BEGIN:VCALENDAR
PRODID:DAVx5/4.4.5-ose ical4j/3.2.19
VERSION:2.0
BEGIN:VEVENT
DTEND;TZID=Europe/Paris:20250102T110000
DTSTAMP:20250131T102215Z
DTSTART;TZID=Europe/Paris:20250102T100000
RRULE:FREQ=WEEKLY;UNTIL=20250227T225959Z;INTERVAL=1;BYDAY=TH
SEQUENCE:1
STATUS:CONFIRMED
SUMMARY:test event
UID:36388a31-16ce-4b9c-910b-c5fa70f25410
END:VEVENT
END:VCALENDAR

2. Reschedule one of the events. This should add a new calendar component to the same calendar object with the RECURRENCE-ID set to the time of the original event in the series which is being rescheduled. However, the calendar app improperly sets the RECURRENCE-ID to the time of the NEW event.

BEGIN:VCALENDAR
PRODID:DAVx5/4.4.5-ose ical4j/3.2.19
VERSION:2.0
BEGIN:VEVENT
DTEND;TZID=Europe/Paris:20250102T110000
DTSTAMP:20250131T102215Z
DTSTART;TZID=Europe/Paris:20250102T100000
RRULE:FREQ=WEEKLY;UNTIL=20250227T225959Z;INTERVAL=1;BYDAY=TH
SEQUENCE:1
STATUS:CONFIRMED
SUMMARY:test event
UID:36388a31-16ce-4b9c-910b-c5fa70f25410
END:VEVENT
BEGIN:VEVENT
DTEND;TZID=Europe/Paris:20250102T144000
DTSTAMP:20250131T102215Z
DTSTART;TZID=Europe/Paris:20250102T134000
RECURRENCE-ID;TZID=Europe/Paris:20250102T134000
SEQUENCE:1
STATUS:CONFIRMED
SUMMARY:test event
UID:36388a31-16ce-4b9c-910b-c5fa70f25410
END:VEVENT
END:VCALENDAR

Expected behavior

The Recurrence ID in the above example should be

RECURRENCE-ID;TZID=Europe/Paris:20250102T100000

Actual behavior

The Recurrence ID in the above example is improperly set to

RECURRENCE-ID;TZID=Europe/Paris:20250102T134000

Screenshots/Screen recordings

No response

Additional information

No response

[barkyq]

I tested with Etar calendar https://f-droid.org/packages/ws.xsoh.etar/ which also uses DAVx5, and it has the correct behaviour.

[naveensingh]

This is somewhat related to #138