macOS Contacts.app sync appears completely broken #1801
Replies: 3 comments 10 replies
-
|
Digging through extensive (and containing a lot of personal information) macOS logs, I found something peculiar. macOS sees the account as having two home collections ... one with principal url of This is most likely macOS bug....Edit: While testing a
|
Beta Was this translation helpful? Give feedback.
-
|
I'm having issues getting MacOS's It seems like the vibe is "Contacts is fickle and some level of broken," so I suppose my results aren't that surprising to the folks here and I shouldn't spend more time on this? As an aside, since |
Beta Was this translation helpful? Give feedback.
-
|
The log shows successful login |
Beta Was this translation helpful? Give feedback.


Uh oh!
There was an error while loading. Please reload this page.
-
Please excuse the title, but I really had no idea what to make of the behavior I observed. This potentially may be multiple issues.
My environment
docker run -p 8443:5232 -v "$PWD/config:/etc/radicale" -v "$PWD/data:/var/lib/radicale" grepular/radicale:3configdirectory;htpasswdpassword istest123)1st attempt - macOS + empty server (failure)
Upon starting the server with empty data/ directory it created a boilerplate structure:
I added the server to macOS Calendar, with information as on the screenshot below, and changed its name upon adding:

Attempting to add a contact produced nothing on the server. However, digging through macOS logs I found:

Nothing worked until I manually created a
data/collections/collection-root/greg/default-addressbook/.Radicale.propswith{"tag": "VADDRESSBOOK"}. I wonder if this has something to do with shenanigans from 12 years ago in #32 whereNo main address book in homeInfowas also reported and fixed? ;)To not pollute the logs I only attempted to add a single contact. Later on I played a bit after adding the prop file and it was somewhat working, but the sync was.... spotty and sometimes required re-editing the contact to get it to sync. However, the biggest problem - and where a bug for sure exists - is adding a second address book redirects all requests to a new-empty address book. macOS doesn't seem to grasp a concept of >1 address book on the server somehow and it will default to the newest one created on the server. Magic :)
Debug attached:
2nd attempt - iOS (success)
I next attempted to start the server with a data directory populated with pure VCFs +
.Radicale.propsacross two address books. I attached this as clean-data.tgz.Next, upon starting the server, I added the server to iPhone:

All contacts synced perfectly. Adding a new one was instantaneously reflected on the server. iPhone doesn't seem to have any issues seeing multiple address books nor user-editable groups:

Deug attached:
3rd attempt - macOS + seed data (failure?)
I seed the
datadirectory with the same clean-data.tgz file from the 2nd attempt and started the server.Contact's app showed me only one of the address books with a single contact:

While adding one worked, I cannot access the other address books and I'm sure adding another empty one on the server will again switch/lock me in the new empty one.
Debug attached:
Help? :)
I honestly don't even know where to start debugging it. I read through the whole v3 docs and I don't see any obvious misconfiguration on my end. I also looked at RFC-6352, as I'm very familiar with HTTP and somewhat with WebDAV, but I don't see anything immediately obvious in the logs that would violate the protocol.
Beta Was this translation helpful? Give feedback.
All reactions