GNOME Bugzilla – Bug 773248
[CalDAV] Google OAuth authentication can fail on refresh
Last modified: 2016-12-13 13:16:09 UTC
Components: evolution.x86_64 3.22.1-2.fc25 evolution-data-server.x86_64 3.22.1-1.fc25 evolution-ews.x86_64 3.22.1-1.fc25 Unable to work with calendar of google accounts, getting: Failed to login to the server: Daily Limit Exceeded. The quota will be reset at midnight Pacific Time (PT). You may monitor your quota usage and adjust limits in the API Console: https://console.developers.google.com/apis/api/caldav/quotas?project=923794261470
This happens for me too. If I add the account via evolution (Through the window shown the first time when evolution is open), I get no issues (until now at least). If I add via GNOME Online accounts, I see this error every now and then. Anyway I closed the bug reported as bug 773203.
I have had this problem for a couple of months. https://bugzilla.gnome.org/show_bug.cgi?id=770265 Now on 3.22.1 and cannot read mail, view calendars or view task lists. "Daily limit exceeded" after gnome-online-accounts (apparently) attempts too many bad connections.
I wrote a bit more details about this here: https://mail.gnome.org/archives/evolution-list/2016-October/msg00124.html
I saw that GOOGLE_CLIENT_ID is hard coded in evolution-data-server and gnome-online-accounts. Is it possible that some other 3rd party software to use these credentials to get the same features? If so is it possible to just use gnome's server as a relay, and get the GOA client id downloaded when required (I think some thing like this happened when gnome maps broke due to discontinuation of previous maps tiles provider)?
(In reply to Mohammed Sadiq from comment #4) > I saw that GOOGLE_CLIENT_ID is hard coded in evolution-data-server and > gnome-online-accounts. Is it possible that some other 3rd party software to > use these credentials to get the same features? It's not hard coded, it's a default, which can be changed during configure time. Taking the secret and client id to some random 3rd-part software would not be fair. Any 3rd-party software can create their own developer account at Google and receive their own ID and secret. Advantage: they would have full control on the ID, not depend on the settings of respective "stolen/borrowed" IDs. > If so is it possible to just use gnome's server as a relay, and get the GOA > client id downloaded when required? I'm sorry, I do not understand the question. Either you use evolution-data-server or GNOME Online Accounts API directly, or not. If not, then you just write from scratch something what is already written and integrated in the desktop. By the way, both questions are rather unrelated to this bug report, or I miss something. (The list members have an idea of changing the developer account for new releases, if your question is similar, then okay, though the 3rd-party acpect of your questions is confusing to me.)
I hope I finally fixed it for the time being, on the CalDAV side, which I believe is the main trouble maker here. Created commit 6a0d294 in eds master (3.23.1+) Created commit 2ca589b in eds gnome-3-22 (3.22.2+)
*** Bug 773342 has been marked as a duplicate of this bug. ***
*** Bug 774172 has been marked as a duplicate of this bug. ***
Please see [1] and if you can, feel free to respond either here or on the list. Thanks in advance. [1] https://mail.gnome.org/archives/evolution-list/2016-November/msg00130.html
*** Bug 774513 has been marked as a duplicate of this bug. ***