after signing into Davx with the same google account on another device, my syncing stopped working and I tried to reset but are now receiving http 400 when trying to sign in. Any recommendations to fix this, as davx5 is important for me to not use the anything google (except the calendar) for what i am doing.

@GEkuL , did you manage to solve the issue? I have the same problem, when following the instructions I only get the contacts but not the calendars.
So far I am using the ICS to fetch the calendars but I would like to have everything under DAVx5.
Thanks!

As I understand it, this is clearly a Google Calendar problem. We could introduce ugly and cumbersome workarounds (like faking a new main event with RDATEs for all instances) for this; but these events as given are not valid. The same behavior would at the latest with CalDAV and r/w calendars cause problems and unsyncable events. Also, I have never seen it from any other client or server.

Do you know whether other iCalendar clients (like Thunderbird, Evolution, Outlook…) can understand these events?

Do you know where to report Google Calendar problems?

Hi @devvv4ever, thanks for the reply.

I have followed these steps and am using the App Password method.
When holding onto the Address Book for carddav and clicking “Properties” within the app, it shows the following Address URL: https://www.google.com/carddav/v1/principals/MYEMAIL/lists/default/
When I visit this URL in my browser, Google just shows a 404.

However, as mentioned, caldav is working as expected, so I think that my setup process was as expected.

Thanks

Hi @rfc2822

thanks for the swift response - this is what I feared. Anyway, your very helpful FAQ page pointed me to a very nice alternative app (Etar) so I can even ditch Google Calendar completely - huray! 🙂

Keep up the great work you are doing on DavX5, I am a very happy long-time user.

All the best,
Simon

@rfc2822 said in [Feature request] OAuth support:

As soon as OAuth is actually adopted by major CalDAV/CardDAV services, implementing it in DAVx⁵ will get higher priority.

For the record, the nextcloud-oidc-login plugin just released v2.1.0 that allows OAuth2/OIDC authentication against the *DAV endpoints.

It works like a charm, for instance with the roundcube rcmcarddav plugin that synchronizes the nextcloud contacts in the roundcube interface.

Not a breaking news though I hope it puts some weight in the balance 🙂

No, Google is the only service with OAuth I know and at the moments, there are no plans in DAVx⁵ to add and maintain OAuth just for Google. 😐

You’re welcome. Nice that it worked out and thanks for the details of what you did.

Thanks @rfc2822, it helps a lot ☺
I managed to sign in with DAVx⁵ using the app password.
Contacts synchronize correctly but aCalendar only wants to sync my main gmail account.
My wife’s gmail account is “forgotten”: it is not in acalendar’s list of calendars, yet it is duly added and associated with my main account
alt text
Why such a restriction? Is the only solution to sign in with DAVx⁵ to my wife’s gmail account?
This solution is not very privacy friendly, it seems to me.

Yes, Google is changing a lot all the time and they deprecated older APIs recently. Some people report its working, but we’ve now disabled the entry again, because it makes too much trouble for us to support a service which constantly changes and which is also not very well tested by Google itself.

@Kim-Heinrich said in Google: Only Carddav is showing up - how do i activate the calendar in DAVx5?:

the URL

Correct URL is here: https://forums.bitfire.at/post/9602

Synchronization with Google CalDAV/CardDAV is not officially supported by Google or DAVx⁵. For some people it seems to work, for others it doesn’t. Google officially requires OAuth 2, which is not supported by DAVx⁵.

We have received updated information about Google CalDAV:

The old endpoint https://www.google.com/calendar/dav is deprecated and no longer supported.
Now you shout suggest https://apidata.googleusercontent.com/caldav/v2/calid/events

Please have a look on https://developers.google.com/calendar/caldav/v2/guide

Google Account security:

If you use 2-Step-Verification for your Google account (recommended): Create an app password for DAVx⁵ and use the app password for signing in with DAVx⁵. If you’re not using 2-Step-Verification: To allow Basic auth clients like DAVx⁵ to connect, you need to “Allow less secure apps” in your Google account before setting up DAVx⁵.

If you have further information, please just post here.

A few weeks ago, Google detected “unusual activity” when I logged into my email from home on a new computer. I was asked to verify my account via a code sent to me via SMS. This resulted in DAVx5 throwing errors and no longer syncing - on a different device. It looked like the Google servers had deemed my home IP address as untrustworthy.

My DAVx5 connection string is: https://www.google.com/calendar/dav/address@gmail.com/events/. So I tried entering that as an address into my browser. A login prompt appeared so I logged in with my email address and password. The attempt failed.

Hmm, is the service no longer running? Then I tried with another account that I had. It worked. Damn, my account is definitely blocked here.

For two weeks I logged into my email from the same IP address. Every time Google required verification via SMS. Boring. During this time DAVx5 was constantly failing.

Then today it let me in without verification. At last, my IP address was trusted as far as my Google account was concerned. And guess what, DAVx5 started working again. Hooray!

So for those of you out there who cannot get DAVx5 to work with your account - or it suddenly stops working - you just have to wait and persevere by logging in daily until the Google servers associate your IP address and your email account together so that other services can log in from there without being blocked.

Hope this helps someone.

Ok my mistake I found the URL listed online, I don’t have that URL off the top of my head…

SORRY I’ll go back and redo it with only that davx URL… My bad…

THANKS

Thanks for the logs. I was finally able to reproduce a similar situation:

Upload an event with UID:a%40b (note the %, for instance coming from some erroneously double-encoded old UID; nevertheless valid) to Google /events/a%40b.ics (or anything else) Google usually rewrites the path (= moves the event) to <UID>.ics, which would be a%40b.ics. However, Google CalDAV REPORT calendar-query reports /events/a%2540b.ics as the URL of the resource. If you want to download /events/a%2540b.ics from Google, it returns 404, although it had just listed this path.

So, in my opinion and what I currently know about it, this seems to be a server problem. It should go away if you delete all events on the server and then only create/sync “clean” events with “good UIDs”. Maybe you can also create a new calendar for testing and see whether this one works?

@devvv4ever , yes, I had to infer the calid (which is a long hex number) from the web UI.
But it didn’t work.

@smac89 said in caldav sync with google doesnt work anymore:

I found this document which states that the correct URL to use is

No. The correct URL is here: https://forums.bitfire.at/post/9602

@Permafrost_39Cel You can install the ICSx app from Google Play ($1.49) or F-Droid (free).

See also: https://davdroid.bitfire.at/configuration/google/