pimutils / pimutils/vdirsyncer
failure using type="google_contacts" (type="google_calendar" works with same client_id, client_secret and token)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.9k
- Forks
- 185
- Avg merge
- 11h 49m
- Merged PRs (30d)
- 1
Description
I get the following error when trying to use the "google_contacts" type.
Note that calendar sync against the same gmail account using the same client_id, client_secret and token are working fine.
vdirsyncer -v DEBUG -c migrate-contacts-user_at_gmail.com-to-localfiles.conf discover
Discovering collections for pair sync_contacts
critical: Failed to initialize user_at_gmail_dot_com
critical: - google_contacts storage doesn't take the parameters: type
Debian Bookworm using the distribution packaged vdirsyncer.
vdirsyncer version 0.19.0
python version Python 3.11.2
migrate-contacts-user_at_gmail.com-to-localfiles.conf:
a = "user_at_gmail_dot_com"
b = "localfiles"
collections = ["from a", "from b"]
conflict_resolution = "a wins"
metadata = ["displayname"]
[storage user_at_gmail_dot_com]
type = "google_contacts"
token_file = "~/.vdirsyncer/token/user_at_gmail.com"
client_id = "redacted"
client_secret = "redacted"
[storage localfiles]
type = "filesystem"
path = "~/.vdirsyncer/archive/local-contact-replicas/user_at_gmail.com"
fileext = ".vcf"
Contributor 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.
Research direction
Start by running the reported vdirsyncer -v DEBUG -c ... discover command with the shown google_contacts configuration, then compare its storage initialization with the working google_calendar setup. Trace where storage parameters are validated; done means the documented credentials and token can initialize google_contacts and discovery proceeds without rejecting type.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100