Chrome Extension store API instructions are outdated

[ggaabe]

Describe the bug
The API instructions point to using an out-of-band api for retrieving an access token. OOB is deprecated and unusable now for new users.
The document here points users to entering a URL with the oob flag in the URL:
https://github.com/GoogleChrome/developer.chrome.com//blob/main/site/en/docs/webstore/using_webstore_api/index.md

Under "Testing your OAuth application".

To Reproduce
Steps to reproduce the behavior:

1. Go to the Testing Your OAuth application section of the chrome store API
2. Enter the URL with relevant credentials
3. See error

Expected behavior
An access token should be provided. Instead there is a deprecation error. The current instructions should be updated to reflect this reality.

[sfoslund]

@AmySteam what are the updated instructions going to be? I am running into this issue and unsure of how to work around it.

[mariuszste]

what are the updated instructions going to be? I am running into this issue and unsure of how to work around it.

The simplest workaround is to just put something fake like http://localhost:1234/whatever in the redirect_uri fields and after you log in then just grab the code from the address bar in your browser when it tries to open the non-existent url. you can then exchange it for a token using the same endpoint as before, you just have to swap redirect_uri to the one you use before.

[mormubis]

Do you happen to have any updates on this? Can you replace OAuth with API Key to avoid these strange use cases?

[oliverdunk]

Thanks for filing this. This is definitely one we are overdue to fix but we already have #3699, so closing as a duplicate of that.