CardDav -> NextCloud in 2.0.4.14 - Rampage stoppable?

I use CalDAV regularly (also on Nextcloud server), and couple of times every week there appear random duplications. I just delete the CalDAV account and create it again on my Jolla, and everything is fine again for a little while. Of course you should always have backups.

I use CalDav and Carddav (nextcloud, before owncloud) since more then a year. There were some breakdowns between, but most time no problems.

If the duplications appear, in calendar app I pull down to the "manage calendars", there all shown twice. Just deselect one of them. After a while, the dupes are gone.

@Robomike In your case, I would delete the caldav and caddav account, depending to your nextcloud installation. If there still address or calendar entry's (same as in nextcould) on the phone, just delete them on the phone. Add a new account, choose caldav & carddav, give the server address with https:// in the beginning. In my case it was not need to provide some extra folder paths. I have auto sync activated since the beginning and never lost any data.

There are a variety of fixes coming in SFOS 2.1.0.x, due to QA improvements (test servers, improved unit tests) and community contributions for issues. So, it could be that a fix for your issue already exists and will be part of 2.1.0.x - but just in case it's not, can you capture sync logs by following the instructions from https://sailfishos.org/wiki/CalDAV_and_CardDAV_Community_Contributions#Sync_Logs and send the results to chris dot adams at jolla dot com so that I can investigate (make sure you redact personal information including usernames, passwords, phone numbers, addresses, etc).

Interestingly, though, local changes should not trigger syncs if the account has Manual sync only selected, so that's clearly a bug - I have filed JB#37054 to investigate this case.

Can you ssh into the device (requires enabling developer mode) and do:

 devel-su
 cd /home/nemo/.cache/msyncd/sync
 ls
 cat carddav*

and look for a key/value setting like:

 <key name="sync_always_up_to_date" value="false"/>

If that doesn't exist, then it seems that the "manual only" setting wasn't stored correctly to the sync profile for that account...

@chris.adams : thanks a lot. I checked the key in the configuration xml and found it set to true. I can switch it by using the settings app, so now I see more clearly that this part of my question was a misunderstanding: I didn't get that apparently the "up to date"-setting overrides the "manual"-setting.

I will investigate the behavior of the syncing after the future update, as you mentioned. With your permission, I will contact you then if I stuck solving the problems.

@poddl : yes, I agree that's best to start with a new setup, but still trying to find out which way is best. After a backup of the contact database or after an export I will delete all data on both ends (better said on all ends, there are some PIM-Clients on several desktop installations waiting for expedient syncings.) But the database seems to be a bit lousy, because of the random duplications, the group definitions and so on. Maybe I should try to manually edit the contacts list and then import it - but where first? Into the phone? Into the nextcloud app? Into Evolution? Into "(KDE-)Contacts"?

Anyway, I will wait until 2.1.0.x is officially released. Maybe I can also switch my server to an official certificate, the self signed certificate is also a big obstacle whilst trying to make it work.

@Robomike I had the best experience with (KDE-)Contacts. It just works without any issues. Edit in Phone or Nextcloud is not very helpful, there are missing fields, like the note field, but Nextcloud leaves this fields untouched and their get synced as well.

In my opinion, certificate is mandatorily with nextcloud and sync stuff. Just use one of the "Let’s Encrypt" project, easy setup, no additional cots.