Extension activation failed: "No access to GitHub Copilot found. #81758
Unanswered
onlyjazz
asked this question in
Copilot Conversations
Replies: 2 comments 1 reply
-
|
I'm facing this same issue under Linux and Windows. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Hello, I have the same problem on macOS. Did you find a solution to the problem? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Bug
Body
I'm unable to activate Github Copilot with a paid Copilot account.
Steps to reproduce
I'm currently logged in to Github as onlyjazz.
I have a paid Copilot account.
I installed Visual Studio Code and GitHub Copilot for VS Code v1.143.0
I get an error message:
[INFO] [auth] [2023-12-24T17:34:56.032Z] Invalid copilot token: missing token: 403
[ERROR] [default] [2023-12-24T17:34:56.033Z] Extension activation failed: "No access to GitHub Copilot found. You are currently logged in as riskgraph."
I have another Github account called riskgraph - but I've refactored all the code into the onlyjazz account and I am not logged into this account on my Mac.
I believe that the bug was caused by the fact that I was logged into my GH riskgraph account the very first time I installed the VS Code plugin.
It seems like a config attribute was set somewhere on the Mac file system that points to riskgraph, this seems to cause the bug
I rm -rf ~/Library/Application Support/Code - and then reinstalled the Copilot extension on the assumption that maybe the riskgraph account was cached over there - but that didn't work
It would be great to have a solution
Danny (@onlyjazz)
Beta Was this translation helpful? Give feedback.
All reactions