-
Notifications
You must be signed in to change notification settings - Fork 83
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
Refresh_token not regenerated with current authorization_url defaults. #348
Comments
I am inclined not to add |
Great point. I'm not sure how best to approach parameterizing or retrying in this edge case. Any thoughts would be helpful. |
you may try this approach. If there is refresh token, just refresh an access token; if we cannot refresh or refresh fails due to expired refresh token, fall back to run_local_server with the url_args, this way you will get a new refresh_token. |
Please reopen the issue if you have any questions. Thanks! |
Thanks for stopping by to let us know something could be better!
PLEASE READ: If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.
Please run down the following list and make sure you've tried the usual "quick fixes":
If you are still having issues, please be sure to include as much information as possible:
Environment details
python --version
pip --version
google-auth-oauthlib
version:pip show google-auth-oauthlib
Steps to reproduce
refresh_token
.Code example
Stack trace
NA -- ValueError
Making sure to follow these steps will guarantee the quickest resolution possible.
Thanks!
Proposed fix (PR incoming)
add
prompt=consent
to theauthorization_url
as a default. As a current workaround I am finding this to work:The text was updated successfully, but these errors were encountered: