I’ll close this issue because I think it’s a duplicate of #51 and it should have been fixed with 0.5.4 (see release notes). Please try with 0.5.4+ (uninstall DAVdroid, install 0.5.4 or later, add account again) and if this issue persists, please comment here and I’ll re-open the issue.
syncing shared address book with nextcloud 11 fails
Short: Davdroid fails on syncing a shared address book with Nextcloud 11
Steps to reproduce:
- Nextcloud: User ‘Michael’ shares an address book ‘testbook’ with the user ‘testacc’ (editable)
- On Android, create a new Davdroid account for the user testacc
- Select ‘testbook’ as addressbook
Outcome: Sync fails with 404 not found errors, see debug here:
What I noticed is, that Davdroid is searching for a contact
while In the Nextcloud interface, the link shown for this addressbook is
the first difference is, that Davdroid is searching at carddav, instead of dav. This shouldn’t be a problem, because carddav is redirected to dav by the server. However, the /users/ shown in the nextcloud interface is missing in the path of Davdroid.
Syncing testacc’s own addressbook works just fine. Any help is appreciated.
Please provide verbose logs so that we can see why
Is there any indication that this could be a DAVdroid problem? Looks like the server advertises
/remote.php/carddav/addressbooks/testacc/testbook_shared_by_Michael/40550d2b-8400-495d-8265-0b540c37713a.vcf, but when DAVdroid requests it, it isn’t there.
here is a verbose log:
I think the log is consistent with your assumption. It seems like the server advertises a vcard that it can’t find later on. I’m not sure, however: There is a passage about a 404 (line 144) in the server’s response, where the vcard is advertised.
Can you tell me how to go on from here? If it’s the server’s mistake, I should probably talk to the nextcloud community?
@sbctm According to the logs, the server advertises this file, but does not provide it (but sends 404 instead). The other 404 in multi-status do not matter.
Please ask Nextcloud people, providing all the logs (or even this thread).
Thanks for your kind advice. I have opened an issue on the nextcloud github page: