Adding start date automatically adds the end date causing sync error #53

Closed
opened 2025-11-01 20:45:35 -05:00 by GiteaMirror · 3 comments
Owner

Originally created by @mzfr on GitHub (May 27, 2022).

So I'm not sure why this was added but if I add "Start date" to the task then "end date" is added.

Now it would have been fine, but I noticed that if a task has an "End date" property, Davx^5 App throws an error stating "received an invalid task from server". When I removed that property it was able to sync fine.

Originally created by @mzfr on GitHub (May 27, 2022). So I'm not sure why this was added but if I add "Start date" to the task then "end date" is added. Now it would have been fine, but I noticed that if a task has an "End date" property, Davx^5 App throws an error stating "received an invalid task from server". When I removed that property it was able to sync fine.
GiteaMirror added the bug label 2025-11-01 20:45:35 -05:00
Author
Owner

@kolaente commented on GitHub (May 27, 2022):

If the task has a due date defined and you define a start date without defining an end date it will automatically use the due date as end date. You should be able to manually remove it though.

Do you have any logs from either the api server or DavX⁵?

@kolaente commented on GitHub (May 27, 2022): If the task has a due date defined and you define a start date without defining an end date it will automatically use the due date as end date. You should be able to manually remove it though. Do you have any logs from either the api server or DavX⁵?
Author
Owner

@kolaente commented on GitHub (Jul 7, 2022):

Looks like this is the problem:

DURATION:PT24.000000H1440.000000M86400.000000S

That duration looks way of.

@kolaente commented on GitHub (Jul 7, 2022): Looks like this is the problem: ``` DURATION:PT24.000000H1440.000000M86400.000000S ``` That duration looks way of.
Author
Owner

@kolaente commented on GitHub (Jul 7, 2022):

Should be fixed in 2b074c60a7 - please check with the next unstable build in ~30 min if it fixes your issue.

@kolaente commented on GitHub (Jul 7, 2022): Should be fixed in https://github.com/go-vikunja/api/commit/2b074c60a736d5ac30d14ef03c1e0e251454473b - please check with the next unstable build in ~30 min if it fixes your issue.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#53