HTTP server error - HTTP 415 Unsupported Media Type
-
@xav I have sent an .apk which drops some unparseable extended properties in order to repair such vCards. Can you uninstall DAVdroid, then install it from the .apk and tell me whether it works?
-
Do I really have to uninstall it first ? My setup became quite dependant on it and I’m afraid it will break things.
-
@xav You can try installing it over the other version. Of course, you should always have backups of everything
Update: But after installing over the other version, you have to
- unselect the address book in DAVdroid,
- force sync and wait until sync is finished (address book is gone),
- select the address book again,
- force sync again.
Otherwise the questionable contacts are not imported again and the new logic won’t be applied. So this is why I recommend to uninstall it – it just makes things easier, and setting up the account again shouldn’t take more than a few seconds.
-
I will do the sync dance, it looks way better for me.
Where can I retrieve that apk ?
-
@xav I have sent it over email
-
Well it seems it’s stuck somewhere. Could you please try to send it to
xav@awak.mobi?
-
@xav Have sent it again, now to this email address
-
OK I received both. It’s not signed with the same key than mine apparently (I got it from F-Droid). I think I’ll have to uninstall and reconfigure everything
-
@xav Indeed. If you use the F-Droid version, you can only update to other F-Droid builds.
-
Sorry for the delay, re-plugging everything was a little tedious. It works very well now, I can modify contacts which were touched by Evolution without error.
Thanks !
-
@xav Thanks for testing. I’m happy that it now works for you.
Can you create a bug report for Evolution so that it won’t create invalid vCards anymore and provide a link for reference here?
-
Done that: https://gitlab.gnome.org/GNOME/evolution-data-server/issues/12 but apparently it wasn’t Evolution’s fault. My contacts list has lived through several clients/servers, I don’t really remember which ones …
-
@xav Thanks. Well, at least it’s now working, and maybe you can determine the suspicious client one day
