Grunt Update Fails and Google Auth Fails

[Greg-Boggs]

We used the older version of this project to build a "best of books" page. We're trying to update to the current version. We do not need access to private sheets, but the build fails with a fatal error.

When I run grunt update, I get this error:

No access token from ~/.google_oauth_token, private spreadsheets will be unavailable. Error: ENOENT: no such file or directory, open '/Users//.google_oauth_token'

We created a google oauth token and when I put it in the path, I then get this error:

Running "sheets" task
(node:5083) UnhandledPromiseRejectionWarning: Error: No access, refresh token or API key is set.

[thomaswilburn]

How did you create the token? There should be a grunt google-auth task that will log in for you and save it in the correct format.

[Greg-Boggs]

The google auth command returns an error from Google:

Authorization Error
Error 400: invalid_request
Missing required parameter: client_id

[thomaswilburn]

Ah, that usually means you do not have a client ID set in your environment variables.

In order to authenticate for the OAuth API, you should follow the instructions in this post. If you're not able to do that, you can publish your book workbook to the web and revert the sheets task to the older, unauthenticated version, but that relies on an older API version and isn't guaranteed to work long-term the way the authenticated version will.

[Greg-Boggs]

Thanks for the replies Thomas. That documentation post is super helpful! I'll give it a try and report back next week.

[Greg-Boggs]

Just incase you're interested, our Library here in Portland uses the app for a best of books list. We're excited to get updated to your current version for the 2021 list.

http://bestof.multcolib.org/2020/

[Anapsys]

I get the same error detailed here.
Following the blog post and creating .google_oauth_token changes the error to a "Error: No access, refresh token or API key is set." on grunt update. Setting the environment variables changes nothing.

[thomaswilburn]

Did you create the token manually, or using the grunt google-auth task? If you create it manually, it probably won't be in the correct format for our authentication process.

[Anapsys]

i cannot use the grunt google-auth command; on launch, it creates the Error 400: invalid request mentioned above.

[Anapsys]

I've since gotten it working. There seems to currently be some issue executing commands to set the environment variables (in windows 10 at least), even from the cloud sdk shell. In the end, I needed to manually add all the environment variables, which then worked on reload.

[Charlotte885]

Hi, i am using debian but i receive Grunt Update Fails and Google Auth Fails. i have put the clientID on .bashrc.