Unable to connect to the GitHub API, please check your internet connection. Refresh appears inoperative.

[kevinsullivan]

Describe the bug

The extension was working, now it's not. Instead, I get the error, "Unable to connect to the GitHub API, please check your internet connection," along with a refresh button. Pressing it appears to do nothing. Nothing visible happens. Similarly, if I run the refresh from the command palette, nothing appears to happen.

To Reproduce

Steps to reproduce the behavior:

I do not know.

Expected behavior

The extension show work, offering me an effective resolution if something's wrong.

Screenshots If applicable, add screenshots to help explain your problem.

You can see in the terminal that I'm online and have access to my repo on GitHub.

Extension Version 0.27.0

Additional context Add any other context about the problem here.

Not a five-star extension, with current version last updated more than half a year ago. Nice while it was working!

[FranciscoG]

This extension is broken. I'm having the same issue and so are other people

I'm seeing this output for the extension:

Activating GitHub Actions extension...
Error getting GitHub context
Bad credentials
HttpError: Bad credentials
.....
....
Cannot fetch github context
Error: Cannot fetch github context
.....
....
Cannot fetch github context
Error: Cannot fetch github context

possible related issue: https://github.com/github/vscode-github-actions/issues/435

[radusuciu]

Also hitting this. Other GitHub extensions work fine.

[Vivihung]

+1 on hitting the same issue. But I have a different trace from GitHub Actions Output in VSCode. The not found error looks odd:

Activating GitHub Actions extension...
Error getting GitHub context
Not Found - https://docs.github.com/rest/repos/repos#get-a-repository
HttpError: Not Found - https://docs.github.com/rest/repos/repos#get-a-repository
    at P (c:\Users\<username>\.vscode\extensions\github.vscode-github-actions-0.27.2\dist\extension-node.js:1:1063039)
    at processTicksAndRejections (node:internal/process/task_queues:105:5)
    at c:\Users\<username>\.vscode\extensions\github.vscode-github-actions-0.27.2\dist\extension-node.js:1:1159359
    at async Promise.all (index 0)
    at c:\Users\<username>\.vscode\extensions\github.vscode-github-actions-0.27.2\dist\extension-node.js:1:1159275
    at c:\Users\<username>\.vscode\extensions\github.vscode-github-actions-0.27.2\dist\extension-node.js:1:1158908
    at De (c:\Users\<username>\.vscode\extensions\github.vscode-github-actions-0.27.2\dist\extension-node.js:1:1158845)
    at os (c:\Users\<username>\.vscode\extensions\github.vscode-github-actions-0.27.2\dist\extension-node.js:1:1339675)
    at Lb.n (file:///c:/Users/<username>/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:112:13382)
    at Lb.m (file:///c:/Users/<username>/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:112:13345)
    at Lb.l (file:///c:/Users/<username>/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:112:12801)

[zuhairmahd]

Hitting this issue on my ARM Surface Pro 11. Strangely it works just fine on my other Intel pcs — same network, same accounts.