github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-06 03:27:53 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

CalDAV - Many changes get reverted on sync #2166

New Issue
Open
opened 2026-03-22 13:56:49 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-03-22 13:56:49 -05:00
Owner
Copy Link

Originally created by @vikunja-bot on GitHub (Apr 1, 2025).

Original issue by dead10ck on 2023-04-02T19:59:53.000Z

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

Original issue on Gitea

@kolaente commented on 2023-04-02T20:34:21.000Z:

Which details specifically? Other than repeating intervals (those are already covered in #1459)

dead10ck commented on 2023-04-02T20:52:57.000Z:

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.

dead10ck commented on 2023-04-02T20:54:25.000Z:

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.

@kolaente commented on 2023-04-03T12:57:21.000Z:

I was not able to reproduce this with a test task in try. Does it work for you there?

dead10ck commented on 2023-04-03T15:51:57.000Z:

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.

dead10ck commented on 2023-04-03T16:01:26.000Z:

Just based on your wording

a test task

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.

@kolaente commented on 2023-04-03T16:16:03.000Z:

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?

dead10ck commented on 2023-04-03T17:20:55.000Z:

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!

@kolaente commented on 2024-12-13T16:25:26.000Z:

is this still a problem?

Originally created by @vikunja-bot on GitHub (Apr 1, 2025). _Original issue by dead10ck on 2023-04-02T19:59:53.000Z_ ### 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_ [Original issue on Gitea](https://kolaente.dev/vikunja/vikunja/issues/1460) --- _**@kolaente** commented on 2023-04-02T20:34:21.000Z_: Which details specifically? Other than repeating intervals (those are already covered in #1459) --- _**dead10ck** commented on 2023-04-02T20:52:57.000Z_: 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. --- _**dead10ck** commented on 2023-04-02T20:54:25.000Z_: 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. --- _**@kolaente** commented on 2023-04-03T12:57:21.000Z_: I was not able to reproduce this with a test task in [try](https://try.vikunja.io). Does it work for you there? --- _**dead10ck** commented on 2023-04-03T15:51:57.000Z_: 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. --- _**dead10ck** commented on 2023-04-03T16:01:26.000Z_: Just based on your wording >a test task 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. --- _**@kolaente** commented on 2023-04-03T16:16:03.000Z_: 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? --- _**dead10ck** commented on 2023-04-03T17:20:55.000Z_: 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! --- _**@kolaente** commented on 2024-12-13T16:25:26.000Z_: is this still a problem?
GiteaMirror added the area/caldav label 2026-03-22 13:56:49 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label area/caldav
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#2166
Delete Branch "%!s()"

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?