Hi,
i am running DAVDroid 1.3.6 on an Galaxy S7 Android 6.0.1.
I installed the CardDAV-Package on my Synology DS215j (DSM 6.0.2-8451 Update 7).
I exported my Contacts on my MacPro from the Contacts App in one big vCard-File and imported this file into the Synology.
Then I synched with DAVDroid and everything looks great. All Contacts are there, I can even add new ones and they are synchronized fine.
When I try to change an existing entry, everything stops working. DAVDroid throws the following Messages (excerpt):
HTTP RESPONSE:
http/1.1 403 Forbidden
Connection: close
Content-Length: 271
Content-Type: text/xml
Date: Wed, 04 Jan 2017 17:40:02 GMT
DAV: 1, access-control, addressbook, extended-mkcol, calendarserver-principal-property-search, calendarserver-principal-search, calendarserver-home-sync
Server: Twisted/13.0.0 TwistedWeb/9.0.0
Strict-Transport-Security: max-age=604800
<?xml version='1.0' encoding='UTF-8'?>[LF]
<error xmlns='DAV:'>[CR][LF]
<no-uid-conflict xmlns='urn:ietf:params:xml:ns:carddav'/>[CR][LF]
<error-description xmlns='http://twistedmatrix.com/xml_namespace/dav/'>Cannot change the UID in an existing resource.</error-description>[CR][LF]
</error>
EXCEPTION:
at.bitfire.dav4android.exception.HttpException: 403 Forbidden
at at.bitfire.dav4android.DavResource.checkStatus(DavResource.java:318)
at at.bitfire.dav4android.DavResource.checkStatus(DavResource.java:291)
at at.bitfire.dav4android.DavResource.put(DavResource.java:202)
at at.bitfire.davdroid.syncadapter.SyncManager.uploadDirty(SyncManager.java:317)
at at.bitfire.davdroid.syncadapter.SyncManager.performSync(SyncManager.java:147)
at at.bitfire.davdroid.syncadapter.ContactsSyncAdapterService$ContactsSyncAdapter.sync(ContactsSyncAdapterService.java:64)
at at.bitfire.davdroid.syncadapter.SyncAdapterService$SyncAdapter.onPerformSync(SyncAdapterService.java:85)
at android.content.AbstractThreadedSyncAdapter$SyncThread.run(AbstractThreadedSyncAdapter.java:272)
SOFTWARE INFORMATION
Package: at.bitfire.davdroid
Version: 1.3.6-gplay (131) Sun Jan 01 12:55:40 GMT+01:00 2017
Installed from: com.android.vending
JB Workaround installed: no
“403, Cannot change the UID in an existing resource” seem to be the interesting bits here. Changing an existing UID is not allowed by the protocol, which is ok, but why does he even try to do that? To get things working again, I have to delete the account in DAVDroid and set it up again. Reverting the change in the adressbook, does not help here …
Any help anyone?
Thanks,
urbZZ