Fails to recognize online account under Gnome 3.8

[who-is-matt]

I'm not sure what the problem is, since I've never used this script before, but I'm getting the following issue under Gnome 3.8:

Logging in as 'None'...
Error logging in as 'None'
'None' may not be a GNOME online account. A list of existing accounts is below.
If you do not see a list of accounts, then you first need to add one.
For more information, see http://library.gnome.org/users/gnome-help/stable/accounts.html
0. xxxxxxxx@gmail.com
Please choose the Account: 0
You choose 'xxxxxxxx@gmail.com'
Logging in as 'xxxxxxxx@gmail.com'...
Error logging in as 'xxxxxxxx@gmail.com'
'xxxxxxxx@gmail.com' may not be a GNOME online account. A list of existing accounts is below.
If you do not see a list of accounts, then you first need to add one.
For more information, see http://library.gnome.org/users/gnome-help/stable/accounts.html

After this, I get the same except that it tries and fails to log into my account instead of "None". I've tried specifying the account using "--account=", but it doesn't change anything. I've obviously already created an Online Account, otherwise it wouldn't be in the list. Maybe Gnome 3.8 changed something about Online Accounts?

[dapolinario]

You can uninstall the application, it is no longer necessary. Only configure the account in Gnome and enable Calendar. Worked for me.

[jayr0d]

Daniel, obrigado for the hint.

True, although only your default calendar is displayed out of the box. In order to add other calendars, you need to add them manually through evolution. If the calendar is not selected to show in list in google, then evolution will not know the calendar is available. Further, you will need to enter your google password twice for each calendar you want to add: once to get the list of calendars from google, and again to add the password for the calendar to the gnome keyring.

[jayr0d]

Does anyone else have this issue under 3.8? I am still using 3.6.

[kamyarkaviani]

Google accounts in Gnome 3.8+ use OAuth 2.0 as opposed to the older OAuth. These two authorization standards are substantially different. oauth.oauth_login needs to be re-implemented.