Big issues with contacts on macOS - finally solved
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- documentation
Research direction
The report describes two CardDAV setup problems: macOS requires the server URL to include https://, and contacts may sync into a different collection. Start by locating the setup instructions and any CardDAV URL or collection handling they describe. Document the confirmed URL requirement and clarify how users can find or select the collection; the issue gives no specific files or tests to start from.
Written by the indexing model from the issue text.
Description
I thought somebody may be interested in this story.
I struggled a lot to get contact sync working on macOS. My calendars worked fine, SSL was set up.
Setup
It turns out that the protocol really matters. Initially I omitted it because the example in the text field was "example.com", just bare. But with the https:// omitted, the mac wouldn't contact the server at all, always responding "Unable to verify account name or password" (even after sometimes allowing adding the account and then asking for the password again later). This also applies to the advanced mode with SSL explicitly enabled.
Actual sync
WIth that out of the way I could finally see my ... where are my contacts? Nothing would show up at all. There wouldn't be any errors and I could create contacts, but they wouldn't show up in my collection. ... it turns out that they showed up in another contacts collection. Not a huge surprise, since at no point did I have to specify which one to use (Apple Contacts has lists for this, but I don't know whether that's also a CardDAV concept). Maybe it would be good to be able to specify which collection to use via the URL. If you already can, it would be nice to have it documented.
My fix was eventually to delete all contacts collections except for the main one. And - oh look - my contacts would appear.
Maybe this report will help somebody with similar frustrations.
These pitfalls should probably be documented or fixed.
- Dominant language
- Python
- Stars
- 332
- Forks
- 61
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from etesync/etesync-dav
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
etesync/etesync-dav#376 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
etesync/etesync-dav#371 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
etesync/etesync-dav#355 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
etesync/etesync-dav#375 · 1 reaction ·
-
PROPFIND on user home returns 500: `ValueError` in radicale `xmlutils.make_clark` (meta keys without `prefix:tag` form)Possibly taken @vitlav claimed this 36 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 30/100
etesync/etesync-dav#372 ·
All issues in etesync/etesync-dav
Similar issues
-
fuzz fuzz-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Switch to ruffOpen
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Qiskit/qiskit-aer#2533 ·
Maintainers usually reply within 1 day
-
crate-drift
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
po4yka/rust-skills#33 ·
Maintainers usually reply within 1 day