You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When starting the local server with npm run watch I got the message saying not containing client_email field. I guess this has to do with Google OAuth.
Am I the only one struggling with this error?
v1.4.1
Node: v15.8.0
Expected Behavior
(local server running correctly)
Actual Behavior
debug: updating tree...
warn: failed updating tree
{
message: 'The incoming JSON object does not contain a client_email field',
stack: 'Error: The incoming JSON object does not contain a client_email field\n' +
' at JWT.fromJSON (/Users/kinoshitaharuki/dev/library/node_modules/google-auth-library/build/src/auth/jwtclient.js:195:19)\n' +
' at GoogleAuth._cacheClientFromJSON (/Users/kinoshitaharuki/dev/library/node_modules/google-auth-library/build/src/auth/googleauth.js:301:16)\n' +
' at ReadStream.<anonymous> (/Users/kinoshitaharuki/dev/library/node_modules/google-auth-library/build/src/auth/googleauth.js:336:40)\n' +
' at ReadStream.emit (node:events:378:20)\n' +
' at endReadableNT (node:internal/streams/readable:1307:12)\n' +
' at processTicksAndRejections (node:internal/process/task_queues:81:21)'
}
The text was updated successfully, but these errors were encountered:
Hi @HarukiKinoshita, would you mind sharing the names of the environment variables you have set in your .env? (Please don't send over the values, those are private!) It seems like something might be slightly misconfigured.
Hello @afischer, I've just sorted out the problem! I mistakenly put OAuth credentials, not the service account credentials, into .auth.json. Sorry for that.
Just one more thing... Heroku builds successfully, but it gets an application error when visiting the application URL. It happens when deploying from my GitHub repo / directly from Heroku CLI. It didn't happen in the initial deploy (from Deploy to Heroku button). Do you have any thoughts?
Ugh... Fixed it. Must have something to do with npm version difference (specify npm 6.x instead of >=6.5.x)
Context (Environment)
When starting the local server with
npm run watch
I got the message saying not containingclient_email
field. I guess this has to do with Google OAuth.Am I the only one struggling with this error?
v1.4.1
Node: v15.8.0
Expected Behavior
(local server running correctly)
Actual Behavior
The text was updated successfully, but these errors were encountered: