-
-
Notifications
You must be signed in to change notification settings - Fork 421
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
InvalidClientIdError in fetch_token() #358
Comments
@djKooks Can you please provide a reproducible test case? |
@singingwolfboy thanks.
Callback come with Could you find something? |
@djKooks Try passing in |
@holsaeter I can confirm that that worked in my case, thanks. ( @singingwolfboy, do you know whether something needs to be done to force an update on readthedocs.io? https://requests-oauthlib.readthedocs.io/en/latest/api.html doesn't reflect the current state of the project and omits the |
@singingwolfboy Sorry to be bringing this old stuff back to life. Found some free time and wanted to cherry pick a few of these issues to clean up. Seems to me that this issue is settled, however, ReadTheDocs is in fact behind. Pulled down the repo, ran [EDIT] Continued reading and found this issue addressing a similar out of sync docs issue: #392 Read the Docs is out of sync. and it looks like that the project needs push out a release to rebuild the documentation. Is there any desire to push a general release update just to get the project on level footing again? If anything get the documentation more current? |
Hello,
I faced an error when go on
fetch_token()
with received url with code and state:Is this known issue? Seems something is being fixed in
fetch_token
in #331 .If this is not fixed, is there a workaround?
Thanks.
The text was updated successfully, but these errors were encountered: