@xuziq2000 I see… Seems like it also works without OAuth2, because DAVx⁵ doesn’t support OAuth.
However your problem seems to be a server problem. Is there is anything specific we can do for you, just let us know.
@sergio Workaround still works (using DAVx⁵ 2.2.1-ose and OpenTasks 1.1.15), however, once I check a task as done in OpenTasks the issue returns with the next sync.
Now I’m using aCalendar+ as calendar app and OpenTasks to sync tasks. When I get a notification for a due task, I just check it as done in the aCalendar+ notification. Notifications from OpenTasks are deactivated. A sync thereafter does not trigger Vibration.
So the Vibration only happens after checking within the OpenTasks notification.
Wenn du den Mac mit iCloud benutzt ist das ein typischer Anwendungsfall den viele User haben. Sowohl die am Mac oder iPhone eingetragenen Termine werden auf der iCloud gespeichert. Am Android richtest du DAVx⁵ mit den Einstellungen für iCloud ein. Du kannst dann auf allen Geräten Termine anlegen, ändern oder löschen. Genauso die Kontakte und Reminder, falls du das willst. Am Android musst du nur sicherstellen, dass neue Termine auch im richtigen Konto (im Dropdown des Termin-Anlegen-Dialoges), nämlich dem DAVx5-icloud-Konto gespeichert werden.
@rfc2822, may application was moved back to the old server.
now all cipherspecs are available again, nothing was changed on the old server !
Only my Nextcloud was first migrated to a newer server, there Nextcloud was updated from 13.0.7 to 14.0.4, the problems occurred.
now the Nextcloud has been moved back to the old server.
But now it is still Nextcloud 14.0.4 !
Could it be that it’s not the cipherspecs but the old DavDroid has a problem with Nextcloud 14.0.4?
To subscribe to the other calendars in my Google Calendar I used the ICSx companion app for DAVx. All public calendars use the ICS format, including the Google-supplied ones like their holiday calendars.
According to the official documentation, DAVx should automatically detect the public ICS calendars integrated with a CalDav calendar and sync them to the ICSx app. That didn’t work for me with my Google calendar so I manually added them to the ICSx app using the URL listed for each of my public calendars at the top of their settings pages. The Google supplied calendars have the iCal url at the bottom of the settings page.
@rparkins said in Sync getting done too late:
However if some devices can in fact start the same sync in parallel, the problem is real.
Yes, but I will only make one level of workaround for these broken devices, not workarounds for the workarounds.
If you could provide information about the device and how this could happen, it would be interesting. Maybe it can be avoided by DAVx⁵, or the problem could be reported to the vendor.
I can only say again that DAVx⁵ does not delete collections from the server unless it’s explicitly requested by the user and confirmed in the UI. Also, we have never heard such a thing before, which is strange when you think how many people uninstall DAVx⁵.
Will mark this is invalid until steps to reproduce or any other indications for this problem are given.