nextcloud caldav sync

[gtubolcev]

... didn't work.
Tryed to enter all cridentials etc. Than "save and connect". "Connecting... Offline mode".
Checked cridentials, they are ok.
UPD: "badStatusCode: 405"
Any help?
Thank you!

[gtubolcev]

Found a solution:
Enter not just https://nextcloud-instance.com but add /remote.php/dav
Should there be a hint in the UI?
Or maybe the app should try to find the right url automatically?

[trougnouf]

Glad you got it :)
Yes a hint would be nice. I already tried to automatically guess the root when a user types a specific calendar instead, some specific serers' well known path would make sense too. I've added #cfait add Nextcloud /remote.php/dav hint to my todo list.

[psxvoid]

FYI: Also, there is another possible issue with nextcloud (at least with my instance). Both Calendar and Tasks apps were uninstalled, I've installed Calendar, successfully configured it in the cfait, Deck: Personal appeared in the app. I've tried to "move" tasks from local to that Deck: Personal but the app crashed and "Local (Recovery)" section appeared. After a bit of research I've discovered that those tasks came from the Deck app which has it's own version of tasks which are probably incompatible with normal tasks. Then I've installed Tasks app in the nextcloud and created a new task collection called "Tasks", then in cfait I've unselected Deck: Personal and selected Tasks collection. It fixed the issue and everything works now.

It might be useful to add some kind of a message/check that the nextcloud server should have both Calendar and Tasks apps installed, and that the app is incompatible with Deck's tasks (though they do appear in the cfait, any creation/modification fails).

Update 1: another issue is that "export local tasks to server" started failing with 405 probably after removing tasks locally on the "server task list"; syncing now always fails with a red exclamation mark on android. Debug export in /data/journal.json contains the following:

      "Move": [
        {
          "uid": "ebb5d77c-83bc-4387-9804-f4409876231b",
          "summary": "test",
          "description": "",
          "status": "NeedsAction",
          "calendar_href": "local://default",
          ...
        },
       "/remote.php/dav/calendars/<user>/tasks/"
       ...

[trougnouf]

Hi @psxvoid ,

Deck does not support 2-way CalDAV synchronization ( nextcloud/deck#2399 , nextcloud/deck#2345 , nextcloud/deck#6859 ). Cfait already had a check for Tasks capabilities, I've added a check for read-only collections so Deck collections should be disabled now. The Android client should also gracefully handle these errors instead of crashing and 405 errors are now part of the unrecoverable errors so tasks should move to the recovery collection instead of being stuck in the journal.

Can you check the current rolling release from https://codeberg.org/trougnouf/cfait/releases ? (Don't install it if you've installed Cfait from Google Play.)

[psxvoid]

Hi @trougnouf ,

Thanks, most of the errors are gone in the rolling release version (I was using 0.5.8 from f-droid).

Though, there is another issue which is most likely caused by the nextcloud itself. I've created some tasks (e.g. task1) in nextcloud, synced, cfait detected the change and created them. Then I deleted it, synced; cfait detected the change and deleted it. Then I'd created task1 again in the nextcloud, synced again, the task appeared in the cfait. Now, when I deleting such task in cfait, I'm getting an error (exclamation mark in the android app inside the sync button). Also note, that there might be some missing steps in between because I'm recalling it roughly. I thought it was caused by something in cfait; but the fact is that deleting the same task in nextcloud fails too. It might not be a direct issue with cfait, but due to this, the sync in cfait is stuck too (the error will never be gone as far as I understand). So maybe something can be done on the app side, e.g. the ability to ignore particular tasks/errors?

And here is what nextcloud log says:

{
    "reqId": "<omitted>",
    "level": 0,
    "time": "<omitted>",
    "remoteAddr": "<omitted>",
    "user": "<omitted>",
    "app": "webdav",
    "method": "DELETE",
    "url": "/remote.php/dav/calendars/<omitted>/tasks/1d9d04ea-679e-4b4a-90dc-f77a1175b4d6.ics",
    "scriptName": "/remote.php",
    "message": "A calendar object with
    URI 1d9d04ea-679e-4b4a-90dc-f77a1175b4d6-deleted.ics already exists in calendar 6, therefore this object can't be moved into the trashbin",
    "userAgent": "<omitted>",
    "version": "32.0.9.2",
    "exception": {
        "Exception": "Sabre\\DAV\\Exception\\Forbidden",
        "Message": "A calendar object with URI 1d9d04ea-679e-4b4a-90dc-f77a1175b4d6-deleted.ics already exists in calendar 6, therefore this object can't be moved into the trashbin",
        "Code": 0,
        "Trace": [{
                "file": "/var/www/html/lib/public/AppFramework/Db/TTransactional.php",
                "line": 45,
                "function": "OCA\\DAV\\CalDAV\\{closure}",
                "class": "OCA\\DAV\\CalDAV\\CalDavBackend",
                "type": "->",
                "args": ["*** sensitive parameters replaced ***"]
            }, {
                "file": "/var/www/html/apps/dav/lib/CalDAV/CalDavBackend.php"

Update 1: here is what journal.json contains:

{
  "queue": [
    {
      "Delete": {
        "uid": "1d9d04ea-679e-4b4a-90dc-f77a1175b4d6",
        "summary": "test1",
        "description": "",
        "status": "NeedsAction",

Update 2: deleting previously deleted tasks with the same name from the trashbin in the nextcloud solves the issue - after doing so, I was able to remove the tasks, and errors disappeared from cfait after a sync.

[trougnouf]

Hi @trougnouf ,

Thanks, most of the errors are gone in the rolling release version (I was using 0.5.8 from f-droid).

Though, there is another issue which is most likely caused by the nextcloud itself. I've created some tasks (e.g. task1) in nextcloud, synced, cfait detected the change and created them. Then I deleted it, synced; cfait detected the change and deleted it. Then I'd created task1 again in the nextcloud, synced again, the task appeared in the cfait. Now, when I deleting such task in cfait, I'm getting an error (exclamation mark in the android app inside the sync button). Also note, that there might be some missing steps in between because I'm recalling it roughly. I thought it was caused by something in cfait; but the fact is that deleting the same task in nextcloud fails too. It might not be a direct issue with cfait, but due to this, the sync in cfait is stuck too (the error will never be gone as far as I understand). So maybe something can be done on the app side, e.g. the ability to ignore particular tasks/errors?

And here is what nextcloud log says:

{
"reqId": "",
"level": 0,
"time": "",
"remoteAddr": "",
"user": "",
"app": "webdav",
"method": "DELETE",
"url": "/remote.php/dav/calendars//tasks/1d9d04ea-679e-4b4a-90dc-f77a1175b4d6.ics",
"scriptName": "/remote.php",
"message": "A calendar object with
URI 1d9d04ea-679e-4b4a-90dc-f77a1175b4d6-deleted.ics already exists in calendar 6, therefore this object can't be moved into the trashbin",
"userAgent": "",
"version": "32.0.9.2",
"exception": {
"Exception": "Sabre\DAV\Exception\Forbidden",
"Message": "A calendar object with URI 1d9d04ea-679e-4b4a-90dc-f77a1175b4d6-deleted.ics already exists in calendar 6, therefore this object can't be moved into the trashbin",
"Code": 0,
"Trace": [{
"file": "/var/www/html/lib/public/AppFramework/Db/TTransactional.php",
"line": 45,
"function": "OCA\DAV\CalDAV\{closure}",
"class": "OCA\DAV\CalDAV\CalDavBackend",
"type": "->",
"args": ["*** sensitive parameters replaced ***"]
}, {
"file": "/var/www/html/apps/dav/lib/CalDAV/CalDavBackend.php"

Update 1: here is what journal.json contains:

{
"queue": [
{
"Delete": {
"uid": "1d9d04ea-679e-4b4a-90dc-f77a1175b4d6",
"summary": "test1",
"description": "",
"status": "NeedsAction",

Update 2: deleting previously deleted tasks with the same name from the trashbin in the nextcloud solves the issue - after doing so, I was able to remove the tasks, and errors disappeared from cfait after a sync.

Those unrecoverable errors are supposed to be detected and their tasks moved to the recovery collection s.t. they stay out of the journal. I have broadened the error detection (in the current rolling release), let me know if you get this issue again (and ideally if an error code is shown).