CalDAV - Many changes get reverted on sync #1460
Labels
No Label
dependencies
duplicate
help wanted
invalid
kind/bug
kind/feature
needs reproduction
question
security
wontfix
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: vikunja/vikunja#1460
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
When using Tasks.org on Android with DAVx for syncing, when many changes are made in between syncs, they seem to be mostly or wholly reverted when synced with Vikunja. I've taken a screen recording of this happening.
Vikunja Frontend Version
0.20.5
Vikunja API Version
0.20.4
Browser and version
No response
Can you reproduce the bug on the Vikunja demo site?
No
Screenshots
No response
Which details specifically? Other than repeating intervals (those are already covered in #1459)
You can see in the video, but specifically on some, I just changed the due dates and those were reverted back to what they were before I changed it. e.g. the one named "Taxes", I only changed the due date from yesterday to today with no other changes, and that was reverted as well. But if I change only that one task and then sync, it syncs successfully with Vikunja. It seems to happen when the are multiple changes queued up that need to be synced.
I just tried it with a few tasks where I only changed the due date and no other details, and this still happens, so it doesn't seem to be related to task recurrence.
I was not able to reproduce this with a test task in try. Does it work for you there?
I was able to reproduce this with this list
https://try.vikunja.io/projects/1/list
You can see I added 5 tasks, labeled "D1" through "D5". I set up CalDAV with DAVx and used Tasks.org to change all the due dates to today at 20:30. It looks like D1 was changed successfully, but the rest were reverted to their previous due date.
Just based on your wording
Did you try it with more than one task at a time? As I mentioned in previous comments, syncing a single task seems to work, but it's when syncing changes to multiple tasks that this problem happens.
I checked this again and it seems to work. I used the caldav integration from within Tasks.org, not DavX5. Does it work with that for you?
Ok I can confirm it doesn't seem to happen with the integrated CalDAV account type, rather than DAVx. So this issue seems specific to DAVx. The integrated client seems substantially slower than DAVx, but at least it works, so I'll use that until the DAVx issue is fixed. Thanks!