10-20 18:56:15.913: E/AndroidRuntime(6921): FATAL EXCEPTION: SyncAdapterThread-1
10-20 18:56:15.913: E/AndroidRuntime(6921): java.lang.NullPointerException
10-20 18:56:15.913: E/AndroidRuntime(6921): at java.net.URI.parseURI(URI.java:353)
10-20 18:56:15.913: E/AndroidRuntime(6921): at java.net.URI.<init>(URI.java:204)
10-20 18:56:15.913: E/AndroidRuntime(6921): at java.net.URI.create(URI.java:725)
10-20 18:56:15.913: E/AndroidRuntime(6921): at java.net.URI.resolve(URI.java:1239)
10-20 18:56:15.913: E/AndroidRuntime(6921): at at.bitfire.davdroid.webdav.WebDavResource.<init>(WebDavResource.java:95)
10-20 18:56:15.913: E/AndroidRuntime(6921): at at.bitfire.davdroid.resource.RemoteCollection.delete(RemoteCollection.java:114)
10-20 18:56:15.913: E/AndroidRuntime(6921): at at.bitfire.davdroid.syncadapter.SyncManager.synchronize(SyncManager.java:53)
10-20 18:56:15.913: E/AndroidRuntime(6921): at at.bitfire.davdroid.syncadapter.DavSyncAdapter.onPerformSync(DavSyncAdapter.java:56)
10-20 18:56:15.913: E/AndroidRuntime(6921): at android.content.AbstractThreadedSyncAdapter$SyncThread.run(AbstractThreadedSyncAdapter.java:257)
401 unauthorized on contacts sync
-
Since 0.6.10.x (F-Droid) if I edit a contact I am no longer able to sync, with error 401 unauthorized. Downgrading to 0.6.8 solve this.
-
We need verbose logs from your phone to look into this issue please. Here is a small tutorial on how you get these logs. https://github.com/bitfireAT/davdroid/wiki/How-to-view-the-logs
-
Is there a reason why you think this is a client problem? 401 means Unauthorized, i.e. wrong user name/password. Maybe the password has changed?
-
@rfc2822 it’s my private server
@devvv4ever thank you, maybe I will try this weekend, I don’t have much time right now. -
@shiba89 I don’t understand the argument. You may also have changed the password on your private server.
But yes, logs and steps to reproduce would be helpful if you think this is a problem of DAVdroid (which could of course be the case, I just have no reasons to think so yet).
-
@shiba89, do you have a self-signed certificate using an IP address only? If so then you might try 0.6.10.1. See also issue #410
-
I found the reason why this happens watching the logs with adb. It seems that owncloud appends @server.hostname.com to every vCard UID field. Since I have had this contact list for several years, some vCard had the hostname of my previous server.
Davdroid <0.6.10 apparently ignores this field, so that’s why I never noticed the problem until now. However since 0.6.10 it tries to sync a modified contact to the server pointed by its UID. Removing every UID solved the problem.
