Same access_token after refresh

[vvscode]

Hey. Is it expected to have the same access token on calling fetch with --refresh?

Just based on the naming I would expect to have different tokens in output, but I do have the same

P.S. the original problem I'm trying to solve is to understand why google API gives me invalid_token while oauth2l info says that token is ok

[andyrzhao]

Hi there, from the top of my head:

1. The refresh parameter is used to refresh expired access tokens (using a valid refresh_token, and skips the user consent screen), so it's possible that the token has not expired, and refreshing was skipped. You can try deleting the cache to force a new token to be fetched.
2. If you get "invalid_token" from google backend, it could be due to using the incorrect scope (normally, you will need cloud-platform as the scope, see ReadMe.) There could also be a formatting error, I wouldn't know until you provide more details.
   Hope that helps!