Closed TPreece101 closed 2 weeks ago
I have same issue too
@azhar22k what exact steps are you trying?
vscode tunneling should work, because the vscode extension runs in a "compute" backend (not directly in the web browser).
Maybe we need to update our isRemoteWorkspace
function: https://github.com/aws/aws-toolkit-vscode/blob/6fa3a9e554f4aa1916d01d00ea93497ca7205cc5/packages/core/src/shared/vscode/env.ts#L103-L104
based on https://github.com/microsoft/vscode/blob/aafaa182180d76bbf0d1e1cd68afa65ec6f407ea/src/vs/platform/telemetry/common/telemetryUtils.ts#L204 it looks like the possible values are:
'ssh-remote'
'dev-container',
'attached-container',
'wsl',
'tunnel',
'codespaces',
'amlext'
https://github.com/aws/aws-toolkit-vscode/pull/5847 may fix this.
Please try the vsix from https://github.com/aws/aws-toolkit-vscode/releases/tag/prerelease
That fixes it for me @justinmk3!
This request was addressed in AWS Toolkit 3.30.0 and/or Amazon Q 1.31.0!
AWS Toolkit changelog: https://github.com/aws/aws-toolkit-vscode/blob/master/packages/toolkit/CHANGELOG.md Amazon Q changelog: https://github.com/aws/aws-toolkit-vscode/blob/master/packages/amazonq/CHANGELOG.md Release artifacts: https://github.com/aws/aws-toolkit-vscode/releases
Problem
When I try to sign in to the Amazon Q VSCode extension via VSCode Web I get an "invalid_grant" error
And when I try to sign in when using tunnelling via the VSCode CLI the OAuth seems to try to direct me to a local URL
Steps to reproduce the issue
Expected behavior
I would expect it to work as it does when I'm just developing locally (that works fine)
System details (run
AWS: About
and/orAmazon Q: About
)