Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Amazon Q features not working in Visual Studio 17.12.0 #478

Closed
awschristou opened this issue Nov 14, 2024 · 1 comment
Closed

Amazon Q features not working in Visual Studio 17.12.0 #478

awschristou opened this issue Nov 14, 2024 · 1 comment
Labels
announcement bug We can reproduce the issue and confirmed it is a bug.

Comments

@awschristou
Copy link
Contributor

On November 12, 2024, Visual Studio 17.12.0 was released. Upgrading to this version causes Amazon Q features to stop working:

  • Amazon Q inline coding suggestions do not appear, and the Output pane titled "Amazon Q Language Client" contains messages textDocument [file:xxxxx] not found
  • Amazon Q security scans fail with the message "Amazon Q security scan failed: Error: Text document for given file is missing."
  • Chatting with Amazon Q Chat about selected code or the currently open file results in responses like "I don't see any code provided to explain."

This has been observed when working with files that automatically open when you load a solution. An issue has been filed with the Visual Studio developer community: https://developercommunity.visualstudio.com/t/VS-1712-not-emitting-document-related-m/10789428

A possible workaround is to close the code file, then re-open it. The Amazon Q features listed above should resume working.
@awschristou awschristou added bug We can reproduce the issue and confirmed it is a bug. announcement labels Nov 14, 2024
@awschristou awschristou pinned this issue Nov 14, 2024
@awschristou awschristou added investigating Issue is being investigated and/or work is in progress to resolve the issue. and removed investigating Issue is being investigated and/or work is in progress to resolve the issue. labels Nov 15, 2024
@awschristou
Copy link
Contributor Author

A fix for this issue has been released in v1.60.0.1 of the Toolkit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
announcement bug We can reproduce the issue and confirmed it is a bug.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@awschristou