-
-
Notifications
You must be signed in to change notification settings - Fork 391
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.
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
[Bug]: Service app may stop working (temporarily lose Accessibility API permission) after update #344
Comments
Please make sure
If you have done the above steps, but the issue persists, please turn on verbose log in the GitHub Copilot settings, and observe the logs in Console.app. You can set the filter to category:GitHubCopilot to see the relevant logs. |
Thanks for the suggestion. Somehow, after restarting my computer it works. However, I would like to mention something that may have to do with the issue. I'm not entirely sure that the issue was an isolated incident. Previously (when the suggestions weren't working) in the "Xcode Inspector Debug" option of the Copilot Service menu bar, I got the following options: After restarting, however, I see those two options filled, with their proper values, and it just so happens that suggestions work again. It seems like previously the service couldn't identify which file was open and active to provide suggestions for. Not sure what happened, I thought I should share this here in case someone else figures out what's causing this issue. |
Before Reporting
What happened?
I was expecting to get suggestions during coding, but I get no suggestions.
How to reproduce the bug.
After updating to version 0.22.2 (I was previously using 0.20), the service stopped providing any suggestions. Even if I go manually to the Editor -> Copilot -> Get Suggestions , I get no suggestions whatsoever. Other apps (like VSCode when used with the appropriate extension) provide suggestions.
Relevant log output
No response
macOS version
13.4.1
Xcode version
14.3.1
Copilot for Xcode version
0.22.2
Node version
v18.16.0 (installed via nvm)
The text was updated successfully, but these errors were encountered: