Please make sure you have searched for information in the following guides.
A screenshot that you have tested with "Try this API".
NA
Link to the code that reproduces this issue. A link to a public Github Repository or gist with a minimal reproduction.
invalid_grant: code_verifier or verifier is not needed
A step-by-step description of how to reproduce the issue, based on the linked reproduction.
- Upgrade googleapis to v150
- npm run dev
- hit localhost:3000
- try to login using your google account
A clear and concise description of what the bug is, and what you expected to happen.
The SDK/API injects a code_verifier prop to the API call data when in fact it shouldn't be there. That's causing an invalid_grant error stating code_verifier or verifier is not needed.
The code_verifier prop should not be injected (it is undefined in the payload).
A clear and concise description WHY you expect this behavior, i.e., was it a recent change, there is documentation that points to this behavior, etc. **
The SDK/API works fine with the same code in versions below 150, so it's likely a change in this version which is causing this behavior. I haven't been able to find documentation around it.
Please make sure you have searched for information in the following guides.
A screenshot that you have tested with "Try this API".
NA
Link to the code that reproduces this issue. A link to a public Github Repository or gist with a minimal reproduction.
invalid_grant: code_verifier or verifier is not needed
A step-by-step description of how to reproduce the issue, based on the linked reproduction.
A clear and concise description of what the bug is, and what you expected to happen.
The SDK/API injects a code_verifier prop to the API call data when in fact it shouldn't be there. That's causing an invalid_grant error stating code_verifier or verifier is not needed.
The code_verifier prop should not be injected (it is undefined in the payload).
A clear and concise description WHY you expect this behavior, i.e., was it a recent change, there is documentation that points to this behavior, etc. **
The SDK/API works fine with the same code in versions below 150, so it's likely a change in this version which is causing this behavior. I haven't been able to find documentation around it.