The Google Auth server issued Refresh tokens never expire — that’s the whole point of the refresh tokens. The refresh token will expire (or I should say become unauthorized) when the user revokes access to your application. Refer this doc it clearly states the function of refresh tokens. Instead of issuing a long lasting token … Read more
To solve this issue, try to: Create a service account: https://console.developers.google.com/iam-admin/serviceaccounts/ In options, create a key: this key is your usual client_secret.json – use it the same way Make the role owner for the service account (Member name = service account ID = service account email ex: thomasapp@appname-201813.iam.gserviceaccount.com Copy the email address of your service … Read more
Although this is an old question, it seems like many still encounter it – we spent days on end tracking this down ourselves. In the OAuth2 spec, “invalid_grant” is sort of a catch-all for all errors related to invalid/expired/revoked tokens (auth grant or refresh token). For us, the problem was two-fold: User has actively revoked … Read more
UPDATE: yes, Google released a public REST API for Keep. Here’s the public documentation.
That error is displayed in case that under “APIs & auth” -> “Consent screen” you have empty field “PRODUCT NAME” – you need to select e-mail address as well. You can find “Consent screen” under a link!, click on project name and then go to “APIs & auth” -> “Consent screen”.
Yes, Google Custom Search has now replaced the old Search API, but you can still use Google Custom Search to search the entire web, although the steps are not obvious from the Custom Search setup. To create a Google Custom Search engine that searches the entire web: From the Google Custom Search homepage ( http://www.google.com/cse/ … Read more