search

gggard / AndroidCaldavSyncAdapater

Caldav synch adapter for Android
246 stars 88 forks source link

Version 1.8.1 fails to talk with OwnCloud 7.0.3 #226

Open mathieumd opened 10 years ago

mathieumd commented 10 years ago

I recently upgraded through F-Droid from AndroidCaldavSyncAdapater 1.8 to 1.8.1, and since then, calendar synchronization constantly fails with an Caldav Synchronization Error (400) message (this is not the exact wording) in the notification area of my Android 4.3.

I am using Owncloud 7.0.3's SabreDAV 1.8.10-stable, and with AndroidCaldavSyncAdapater 1.8.1, the log shows:

<IP> - - [19/Nov/2014:09:47:56 +0000] "PROPFIND /remote.php/caldav/principals/mathieu HTTP/1.1"
 400 6627 "-" "CalDAV Sync Adapter (Android) https://github.com/gggard/AndroidCaldavSyncAdapater
 Version:1.8.1"

While, with AndroidCaldavSyncAdapater 1.8, it works:

<IP> - - [19/Nov/2014:09:51:11 +0000] "PROPFIND /remote.php/caldav/principals/mathieu HTTP/1.1"
 401 304 "-" "CalDAV Sync Adapter (Android) https://github.com/gggard/AndroidCaldavSyncAdapater
 Version:1.8"
<IP> - mathieu [19/Nov/2014:09:51:12 +0000] "PROPFIND /remote.php/caldav/principals/mathieu HTTP/1.1"
 207 1546 "-" "CalDAV Sync Adapter (Android) https://github.com/gggard/AndroidCaldavSyncAdapater
 Version:1.8"

I downgraded to 1.8 and now synchronization works back.

kupschke commented 10 years ago

It works with following workaround in owncloud:

http://forum.owncloud.org/viewtopic.php?f=29&t=24783#p73174

ujojesita commented 9 years ago

Same problem, suggested link above did not help. Synchronization by Solcalendar works.

smu commented 9 years ago

Same here, but workaround works for me.

justPoppingIn commented 9 years ago

Same problem here. Suggested link did not fix the problem. Caldav shows a synchronization problem (connection reset by peer). All other clients work well with owncloud 7.0.3 (thunderbird lightning with inverse sogo connector). Problem was not there with previous owncloud versions.

Update It's working again, sorry for the false alarm. For those interested - It was a DNS issue. I use DDNS and the ISPs DNS-Server of my mobile phone stopped updating the IP. Fixed it with the app DNSet that uses a different DNS-Server.