Added Google Account does not add/show Calendar (only shows Contacts) on GrapheneOS

[cytopia]

Description

When adding a new Google Account via the Option Add account -> Google Contacts / Calendar, it always only creates a Contact Sync, but no Calendar. I have already uninstalled and reinstalled the App, but it doesn't fix the issue.

In my Google Account I can see that it has requested the Contacts as well as the Calendar permissions successfully.

Versions

• Running GrapheneOS stable (Android 14 - Sec update: Dec 5th)
• DAVx5 4.3.11-ose (4031100004) Compiled on 11/22/2023 (installed via F-Droid)

Question

How can I caldav sync my Google Calendar with DAVx5?

Potential similar tickets

• Caldav not shown when using Google account and own Client ID #356

Steps to reproduce:

1. 
2. 
3. 
4. 
5. 
6. 
7. 

[cytopia]

I have now switched to the OAuth Client ID method. For that I have created the App according to the documentation available in the youtube video:
https://www.davx5.com/tested-with/google/

However, upon logging into my account via DAVx5 (email address and OAuth Client ID set), I am presented with the following screen:

When swiping back, I get a small popup message at the bottom of the screen saying:

Couldn't obtain authorization code

I have already tried prepending http:// or https:// to my OAuth Client ID, but that also doesn't help. How do I figure out, what exactly is wrong with my current approach?

And second question: Do I need to start the free Cloud trial in order for it to work?

[rfc2822]

Did you give CalDAV/CardDAV permissions to the client ID?

I'd however not create a custom Client ID, because it's not necessary at the moment. You can enable Verbose logging in DAVx5 settings, then add your Gmail account and then see in the logs why the detection of CalDAV failed.

[cytopia]

Did you give CalDAV/CardDAV permissions to the client ID?

Yes, I followed the complete Youtube Video on how to set this up. The only thing I left out (which was not part of the Video, but I found it later in the text is to validate my account via credit card)

I'd however not create a custom Client ID, because it's not necessary at the moment. You can enable Verbose logging in DAVx5 settings, then add your Gmail account and then see in the logs why the detection of CalDAV failed.

Hmm the approach without Client ID (by using OAUTH login) just gives me CardDav and no Calendar (as written in my first post). 🤔

[rfc2822]

Hmm the approach without Client ID (by using OAUTH login) just gives me CardDav and no Calendar (as written in my first post). 🤔

Yes, I understood that – to find out why, you can use the verbose logs.

[cytopia]

So, after looking back at this I saw that the sync started working. I haven't changed anything (neither on my Google account nor on the DAVx5 config) and it started working all on its own 🤷

I then removed this account (with custom client ID) and wanted to try the normal OAUTH with verbose logging... It now also shows the calendar. I'm a bit lost as I haven't done anything and it just works.

I will close this ticket and re-use it in case I'll face the issue again.

Thank you for trying to troubleshoot this with me!

[zubieta]

I believe I was able to reproduce this. The problem happened to me when I clicked Sing in with Google without filling in the Google account input form.

But once I removed the account and added it again filling in the Google account everything worked flawlessly. I was able to reproduce it three times while adding the accounts.

This is a wild guess, but I think that the value of the Google account form is being used during the CalDav discovery instead of the account email returned in the Oauth flow.

[rfc2822]

This is a wild guess, but I think that the value of the Google account form is being used during the CalDav discovery instead of the account email returned in the Oauth flow.

We don't even request the email address, as this would require another scope (= permission) and from a Google side, it would probably mark DAVx5 as "this app collects your email" with new approval process etc

The email field was never intended as optional. The next davx5 version will enforce this.

[cytopia]

So that means you have to enter your google account email into the "Google Account" input field before clicking on "Sign in with Google" ?

[rfc2822]

Yes. The next DAVx5 version will enforce this so that you can't even click Sign in with Google without entering your email address.

See also #525 (comment)

[seadowg]

I'm seeing exactly the same problem in the latest version (4.4.0.1-gplay). To reproduce:

1. Click Add account
2. Choose Google Contacts / Calendar and then click Continue
3. Fill in Google account and click "Sign in with Google"
4. Sign in and return

I see the "Contact group method" option and then it jumps back to the account where I only have a CardDAV tab. In my Google account, DAVx is connected with access to the calendar:

[rfc2822]

Does it work with 4.4.1-alpha.1 from here?

[seadowg]

Yup that's fixed it!