Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Google has deprecated OOB OAuth Flows

See original GitHub issue

Update:

We put out a guide on how to fix this.

As of Feb 28th 2022, Google has deprecated OOB OAuth flows.

Just a heads up as the documentation to get the refreshToken relies on the oob flow, and we’re seeing 400s when trying to go through that flow.

Example:

Issue Analytics

State:
Created 2 years ago
Reactions:5
Comments:27 (8 by maintainers)

Top GitHub Comments

16reactions

louisgvcommented, Apr 19, 2022

Just released gcp-refresh-token, source code here.

Let me know if you have any issue (preferably creating an issue under gcp-refresh-token). To use, download your OAuth Client json key into a key.json file, then run:

npx gcp-refresh-token

# or

pnpm dlx gcp-refresh-token

Refers to the readme and this updated guide for more info!

–/U64eCftcNBXxHZRu3

2reactions

fregantecommented, Apr 7, 2022

From the linked post, it seems that the temporary fix is to add a &ack_oob_shutdown=2022-10-03 parameter to the URL. Can anyone try? PR welcome if that works.

I think that the tokens generated this way will continue being valid, the problem here is just the process itself (which I’ll have to update at some point)