In the last week, you might have noticed a few strange errors popping up for your Google accounts or even problems setting up Google accounts at all.
Update 12/09/2019: We are happy to announce that after 4 months we were able to get this annoying error sorted with Google oAuth support.
The problem was two-fold - the quota for synchronizing contacts in a single day was set too low but this setting was also invisible for our developers.
We have been sending nearly daily messages to the Google team and finally they resolved both of these issues.
The Contacts API quota is now visible, so our developers can monitor it and the actual quota for our application has been bumped up and all our users are covered now.
Thank you everyone for your patience and understanding while we were doing our best to get Google to sort out this server issue and thanks to everyone who reached out to them on our behalf.
UPDATE 08/21/2019: It seems the Contacts quota issue has not been resolved after all, we have followed all instructions provided by Google support and are now waiting for resolutions from their side. There is unfortunately no change we can make to fix this issue, it needs to be stopped from the server side.
We are very sorry for the inconvenience.
You were affected if you have seen an error like this:
Synchronizing folder list failed due to the following error: Execution of request failed: https://www.google.com/m8/feeds/groups/default/full?start-index=1&max-results=2147483646 ({
"error":{
"code": 429,
"message": "Quota exceeded for quota metric 'contacts.googleapis.com/default'
and limit 'defaultPerDayProject' of service 'contacts.googleapis.com' for
consumer 'project_number:920743529221'.",
"status": "RESOURCE_EXHAUSTED",
"details": [
{
"@type": "type.googleapis.com/google.rpc.Help",
"links": [
{
"description": "Google developer console API key",
"url": "https://console.developers.google.com/project/920743529221/apiui/credential"
}
]
}
]
}
}
)
The problem was connected to the OAuth login for our application and was resolved in cooperation with Google support.
Thanks to everyone who reported the issue so we could bring it to their attention.