Access token coming from Sign In With Google often contains scopes requested at sign-in, but sometimes doesn't.
Expected behavior
Access token should always contain requested scopes. This can be done by explicitly specifying the scopes when requesting an access token.
Reproduction
This is from a race condition, so it cannot be reliably reproduced.
Steps to reproduce
This is from a race condition, so it cannot be reliably reproduced. My end users are affected, and I have identified and tested a fix: nkalupahana/baseline#401
Other information
I will be submitting a PR that fixes this shortly (today).
Plugin(s)
Version
6.1.0
Platform(s)
Current behavior
Access token coming from Sign In With Google often contains scopes requested at sign-in, but sometimes doesn't.
Expected behavior
Access token should always contain requested scopes. This can be done by explicitly specifying the scopes when requesting an access token.
Reproduction
This is from a race condition, so it cannot be reliably reproduced.
Steps to reproduce
This is from a race condition, so it cannot be reliably reproduced. My end users are affected, and I have identified and tested a fix: nkalupahana/baseline#401
Other information
I will be submitting a PR that fixes this shortly (today).
Capacitor doctor
Before submitting