chrome-addon icon indicating copy to clipboard operation
chrome-addon copied to clipboard

Logging the actual response for "Request failed with status code 400"

Open tiratatp opened this issue 4 years ago • 5 comments

I've tried enabling the debug logging as mentioned in #4,

This is all there is,

2020-04-24T15:41:28.4563154Z ##[debug]Evaluating condition for step: 'Chrome Addon Action'
2020-04-24T15:41:28.4568033Z ##[debug]Evaluating: success()
2020-04-24T15:41:28.4568311Z ##[debug]Evaluating success:
2020-04-24T15:41:28.4568982Z ##[debug]=> true
2020-04-24T15:41:28.4569349Z ##[debug]Result: true
2020-04-24T15:41:28.4571155Z ##[debug]Starting: Chrome Addon Action
2020-04-24T15:41:28.4627060Z ##[debug]Loading inputs
2020-04-24T15:41:28.4630477Z ##[debug]Evaluating: secrets.CHROME_CLIENT_ID
2020-04-24T15:41:28.4631511Z ##[debug]Evaluating Index:
2020-04-24T15:41:28.4631708Z ##[debug]..Evaluating secrets:
2020-04-24T15:41:28.4632003Z ##[debug]..=> Object
2020-04-24T15:41:28.4632264Z ##[debug]..Evaluating String:
2020-04-24T15:41:28.4632473Z ##[debug]..=> 'CHROME_CLIENT_ID'
2020-04-24T15:41:28.4633285Z ##[debug]=> '***'
2020-04-24T15:41:28.4634055Z ##[debug]Result: '***'
2020-04-24T15:41:28.4635387Z ##[debug]Evaluating: secrets.CHROME_CLIENT_SECRET
2020-04-24T15:41:28.4635573Z ##[debug]Evaluating Index:
2020-04-24T15:41:28.4635779Z ##[debug]..Evaluating secrets:
2020-04-24T15:41:28.4636065Z ##[debug]..=> Object
2020-04-24T15:41:28.4636271Z ##[debug]..Evaluating String:
2020-04-24T15:41:28.4636694Z ##[debug]..=> 'CHROME_CLIENT_SECRET'
2020-04-24T15:41:28.4637202Z ##[debug]=> '***'
2020-04-24T15:41:28.4637956Z ##[debug]Result: '***'
2020-04-24T15:41:28.4639054Z ##[debug]Evaluating: secrets.CHROME_REFRESH_TOKEN
2020-04-24T15:41:28.4639248Z ##[debug]Evaluating Index:
2020-04-24T15:41:28.4639404Z ##[debug]..Evaluating secrets:
2020-04-24T15:41:28.4639649Z ##[debug]..=> Object
2020-04-24T15:41:28.4639850Z ##[debug]..Evaluating String:
2020-04-24T15:41:28.4640042Z ##[debug]..=> 'CHROME_REFRESH_TOKEN'
2020-04-24T15:41:28.4640682Z ##[debug]=> '***'
2020-04-24T15:41:28.4640978Z ##[debug]Result: '***'
2020-04-24T15:41:28.4641613Z ##[debug]Loading env
2020-04-24T15:41:28.4645302Z ##[group]Run trmcnvn/chrome-addon@v2
2020-04-24T15:41:28.4645409Z with:
2020-04-24T15:41:28.4645519Z   extension: kinpgphmiekapnpbmobneleaiemkefag
2020-04-24T15:41:28.4645624Z   zip: dist/chrome.zip
2020-04-24T15:41:28.4645893Z   client-id: ***
2020-04-24T15:41:28.4646103Z   client-secret: ***
2020-04-24T15:41:28.4646307Z   refresh-token: ***
2020-04-24T15:41:28.4646417Z ##[endgroup]
2020-04-24T15:41:28.6234974Z ##[error]Request failed with status code 400
2020-04-24T15:41:28.6285593Z ##[debug]Node Action run completed with exit code 1
2020-04-24T15:41:28.6286741Z ##[debug]Finishing: Chrome Addon Action

Is it possible to log the actual response or the error message so we can understand what was causing this 400?

tiratatp avatar Apr 24 '20 15:04 tiratatp

It looks like this may not be possible, which is why PR #13 was created. Merging that, and adding a link to it might help.

mrmckeb avatar Jan 11 '21 14:01 mrmckeb

I have 403 error. In debugging logs unfortunately no response information. There are plenty of reasons for this type of error, any suggestions on how to see a response?

Semro avatar Aug 01 '21 20:08 Semro

I still have this issue and I do just for chrome a manual release.

Mte90 avatar Sep 16 '21 08:09 Mte90

Have this issue too. Refreshing Id, secret and refresh token didn't help

UPD: Adding two-step verification on https://www.google.com/landing/2step did helped

XFox111 avatar Sep 17 '21 14:09 XFox111