You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Signing in issue - Error: The authentication flow did not complete successfully, and Cloud Code for VS Code is not authorized to access your account.
#867
Closed
gpwalczak opened this issue
Nov 23, 2023
· 5 comments
Error: The authentication flow did not complete successfully, and Cloud Code for VS Code is not authorized to access your account.
I am failing to Sign in to Cloud Code and docs do not provide further insights beside the error message above. Does it mean the org admin disabled the access for this app for my account? How should I progress with troubleshooting to unblock from this?
Hi @gpwalczak we're currently working on rolling a fix to common authentication issue in Cloud Code, build should be live sometime next week (2.2.0).
The error above usually means something to do with admin access or an issue fetching the exchange token from google auth server. If you still run into the issue again, please file a feedback using the in product feedback button:
And also please ensure "Send Cloud Code logs" is checked
Hi @darkthecross can you help us identify the specifics in the Cloud Code logs above? You can use the in IDE "Report a Bug / Request a Feature" form to send the logs. Thanks!
Looks like this can be caused by authentication service in GCP having transient issue. If you see consistent failure please follow the above steps to send us detailed logs.
Error: The authentication flow did not complete successfully, and Cloud Code for VS Code is not authorized to access your account.
I am failing to Sign in to Cloud Code and docs do not provide further insights beside the error message above. Does it mean the org admin disabled the access for this app for my account? How should I progress with troubleshooting to unblock from this?
Note I have added "https://accounts.google.com" to trusted domains.
The text was updated successfully, but these errors were encountered: