Editing a date creates a new date beside the old one
Checklist
- [X] I can reproduce the bug with the latest version given here.
- [X] I made sure that there are no existing issues - open or closed - to which I could contribute my information.
- [X] I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
- [X] I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
- [X] I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
- [X] This issue contains only one bug.
- [X] I have read and understood the contribution guidelines.
Affected app version
1.0.2
Affected Android/Custom ROM version
Android 13/ LineageOS 20
Affected device model
Samsung Tab S6 lite
How did you install the app?
F-Droid / IzzyOnDroid
Steps to reproduce the bug
I have a permanent appointment in the calendar: at the same time every week. I had to reschedule an appointment for the day before with a different primeval time. So I edited the appointment and when saving it answered the question: "Change only the selected appointment". Afterwards, the old appointment was still available and a new appointment with the changed data was created. I did this again with the same result.
Expected behavior
The old date should be changed
Actual behavior
a new date is created
Screenshots/Screen recordings
No response
Additional information
No response
Hi, Me and @Yaassiihh from University have to validate a courses in which we have to participate to an open-source software. This bug looks interesting and we would like to fix it.
Hi, Just wanna keep you informed that we fixed the issue and we will create the pull request soon.
Note: This also happens with daily repeating events. To fix this, the exception date must be updated in the local DB as well as the Android calendars db.
Same issue with me. APP version 1.0.3 // Android 11 - LineageOS 18.1 // F-Droid
Any fix for the problem in the pipeline? The problem was already mentioned with SimpleCalendarPro, but there was never a solution.
https://github.com/SimpleMobileTools/Simple-Calendar/issues/1538