Bug 1385825

Summary: Google CalDav API Daily Limit for Unauthenticated Use Exceeded.
Product: [Fedora] Fedora Reporter: lray+redhatbugzilla
Component: gnome-online-accountsAssignee: Debarshi Ray <debarshir>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: bugzilla, debarshir, hancockrwd, jan.vesely
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-31 10:01:22 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description lray+redhatbugzilla 2016-10-17 18:36:03 UTC
Description of problem:
Trying to retrieve updates on calendar using goa google caldav adapter returns the message 

"Daily Limit for Unauthenticated Use Exceeded. Continued use requires signup"

Version-Release number of selected component (if applicable): 

How reproducible: Use GOA Google adapter, open Evolution and tyu to send/receive changes.

Actual results:


"evolution[2790]: Failed to call a DBus Proxy method org.gnome.Evolution.Module.ItipFormatter.WebExtension::ShowCheckbox: Part ID '.message.mixed.1.itip' not found
Okt 17 20:31:19 nightlife-local gnome-calendar[16939]: source_credentials_required_cb: Failed to authenticate 'Contacts': Anmeldung am Server fehlgeschlagen: Daily Limit for Unauthenticated Use Exceeded. Continued use requires signup."

No calendar data shown in gnome calendar.


Expected results:

No error message. Calendar data shown.

Additional info:

Comment 1 Heiko Adams 2016-10-17 20:01:58 UTC
Can confirm this with latest goa package installed:
$ rpm -q gnome-online-accounts
gnome-online-accounts-3.22.1-1.fc25.x86_64

Comment 2 Debarshi Ray 2017-01-31 10:01:00 UTC
*** Bug 1350678 has been marked as a duplicate of this bug. ***