CardDav broken after upgrade to El Capitan

Question

InspiredLife Author

Level 1

69 points

CardDav broken after upgrade to El Capitan

Today I upgraded from 10.10.5 to 10.11.6

One issue I have is that the CardDav account (which is set up in my OS X Accounts) no longer works.

In Contacts.app that CardDav address book produces this error:

The operation couldn’t be completed. (CoreDAVErrorDomain error 3.)

The above error appears when I click on the little ! triangle.

Is there a suggested way to go about fixing this?

MacBook Pro, OS X El Capitan (10.11.6), 256 SSD, 1TB HDD, 8GB RAM, Matt 17"

Posted on Aug 7, 2016 11:04 AM

Reply

Answer 1

InspiredLife Author

Level 1

69 points

Aug 7, 2016 11:18 AM in response to InspiredLife

UPDATE: I disabled the account (in Contacts.app), then restarted Contacts. Obviously, only local contacts were displayed. I then enabled it again, and restarted Contacts, but it has no reappeared in the sidebar. Just local contacts are there.

I tried adding a new account (with exactly the same credentials as the existing entry) and it can't log into the server.

Reply

Answer 2

InspiredLife Author

Level 1

69 points

Aug 7, 2016 3:49 PM in response to InspiredLife

(seems I can't edit my original post)

I have read through the 5 pages of posts at: Re: el capitan cardDAV sync broken?

But it appears to me the issue was never resolved. That thread needed back in 2015. New versions of OS X and OwnCloud have been released since then.

I have Owncloud 8.2.7. I have also installed a temp install of 9.1 to see if the issue still occurs. In my case it does.

I've been successfully using OwnCloud for about 3 years, on all versions of OS X I've been on in that time... up to 10.10.5, from which I upgraded to 10.11.6, at which point the CardDAV sync died.

In the above mentioned discussion, there was suggestions of adding some redirect rules (2) to either the Apache .conf file, or to the .htaccess file. I don't have access to the Apache cons files (shared hosting), so I added it to the .htaccess file in the root of the site.

My OwnCloud install is in a subfolder, /ocloud/

If any more info is needed in order to help my troubleshoot this issue, please advise.

Thanks,

Jonathan

Reply

Answer 3

Sep 20, 2016 1:50 PM in response to InspiredLife

Basically, what you can try is alter the sandboxing behaviour.

First check your console after you launched contacts for lines like these:

Contacts(3186) allow mach-register com.apple.AddressBook.AddressBookApplicationFrameworkIPC

com.apple.Addres(3189) deny network-outbound /private/var/run/mDNSResponder

Failing after a number of tries.

If you don't see something like that don't follow the next steps. You will find more information that might help.

You will have to edit a basic system-file by following the guide here: https://gist.github.com/mems/57a34fcf89441ae96b0d

Please be carefull and know what you are doing. Having a backup is always a good idea. Altering systemfiles is not why we all have bought a mac. But it seems like Apple doesn't really care since this problem is with us since the betas of 10.11.

For now I somehow fixed the issue by altering the .htaccess file so the OS X Dialogue recognizes the path. It seems somewhat irrellevant what server path you put into the dialogue. When you check it later - it reads something different, than what you put in. (bug)

I'm on 10.11.6 and currently change from owncloud to nextcloud, but it's almost the same for now. iDevices sync fine as my old Macbook Pro on 10.8.5

The procedure with .htaccess and changing the systemfile made my sync somehow bearable. However it still looks not 100% reliable. Deleting and adding contacts works good, but updating not so much... Still checking that out.

Reply