pimutils / pimutils/vdirsyncer

No collection found on Google Workspace calendars - is there any way to sync a specific CalDAV calendar to a specific Google calendar?

Open
#1,079 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
1.9k
Forks
185
Avg merge
11h 49m
Merged PRs (30d)
1

Description

Before you submit bug reports: https://vdirsyncer.pimutils.org/en/stable/contributing.html

Things to include in your bugreport:

Question Response
Your vdirsyncer version 0.19.1
If applicable, which server software (and which version) you're using ?
Your Python version Python 3.10.10
Your operating system Alma Linux 8.7
Your config file https://privatebin.net/?d900aa68dba5b714#8wbzSmF6iUFFkBmLxPbJmbMpBKthSpmSR4jcBD6rMFrM - Password: bunbunCARROT33!

Use vdirsyncer -vdebug for debug output. The output is sensitive, but please attach at least the last few lines before the error (if applicable), censored as necessary. This is almost always the most useful information.

vdirsyncer Baikal CalDAV to Google CalDAV sync:

This is the shell output from a vdirsyncer discover with the Google side set as type = "caldav", but there's a link to the full and sanitized version (with password) down below.

$ vdirsyncer discover
Discovering collections for pair example
baikal_example_local:
  - "default" ("Example")
google_example_remote:
  - "events" ("exampleadmin@gmail.com")
warning: No collection "default" found for storage google_example_remote.
Should vdirsyncer attempt to create it? [y/N]: y
error: The server returned something vdirsyncer doesn't understand. Error message: InvalidXMLResponse("Couldn't find home-set.")
error: While this is most likely a serverside problem, the vdirsyncer devs are generally interested in such bugs. Please report it in the issue tracker at https://github.com/pimutils/vdirsyncer/issues

https://privatebin.net/?48cc4691573cc2d5#6PQ4TBiAbit9kCoZidDQAJj83gcPxkWYSeezoU8goMNK

Password: catsRneat42!

vdirsyncer Baikal CalDAV to Google Calendar

This is the shell output from a vdirsyncer discover with the Google side set as type = "google_calendar", but there's a link to the full and sanitized version (with password) down below.

$ vdirsyncer discover
Discovering collections for pair example
baikal_example_local:
  - "default" ("Example")
google_example_remote:
  - "example_admin@gmail.com"
  - "c_58ee7c9c7b763723176d295554811ab5c23c629515cee7f497fe6cdc87968b6c@group.calendar.google.com" ("default")
warning: No collection "default" found for storage google_example_remote.
Should vdirsyncer attempt to create it? [y/N]: y
error: 400, message='Bad Request', url=URL('https://apidata.googleusercontent.com/caldav/v2/example_admin@gmail.com/default')
critical: Unable to find or create collection "default" for storage "google_example_remote". Please create the collection yourself.

https://privatebin.net/?f31a80e704742d20#516ZyKLaFi7cH8KWTWjmb8QbyYRCmVQxXkYVTXSdXV4f

Password: catsRneat42!

Basically, it doesn't seem like there's a way to specify WHICH calendar on Google to synchronize to - and I get this error regardless of whether or not I try to synchronize Google via the type = "caldav" or type = "google_calendar" in my config file.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the vdirsyncer discover entry point and compare the configuration behavior for type = "caldav" and type = "google_calendar". Determine how a specific Google calendar can be selected or created, then verify that discovery no longer reports a missing collection or home-set error for the requested calendar.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.