github / github/app

Windows app 1.1.21 hangs during GitHub authentication without generating a device code

Open
#3,935 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
2.1k
Forks
157
PR merge metrics
No merged PRs in 30d

Description

Short summary

The Windows GitHub Copilot app gets stuck during GitHub authentication. It displays Opening GitHub.com to authorize... and then shows - - - - - - - - with Copying code to clipboard..., but never generates an actual device code.

Affected version or release

GitHub Copilot app 1.1.21

Installation context

Windows 11. Installed for the current Windows user. The issue affects the Windows GitHub Copilot app only. Copilot CLI in WSL remains installed and functional (version 1.0.83).

What happened?

After installing GitHub Copilot for Windows and attempting to sign in to GitHub, the app displays:

Opening GitHub.com to authorize...

The device-code field remains:

- - - - - - - -

and the app displays:

Copying code to clipboard...

The app remains stuck indefinitely and never provides an actual device code.

The GitHub device authorization page (https://github.com/login/device) can be opened successfully in the browser, and the GitHub account is already signed in there. Windows clipboard functionality also works normally.

I completely removed the Windows GitHub Copilot app and its app-specific WebView2/application data, rebooted Windows, and reinstalled version 1.1.21. The exact same authentication problem occurs after the clean reinstall.

The Copilot CLI in WSL works independently, and it was not modified during this troubleshooting.

While the Windows app is stuck, the github.exe process has local 127.0.0.1 connections but no established direct remote HTTPS (:443) connection.

Steps to reproduce

  1. Install GitHub Copilot app 1.1.21 on Windows 11.
  2. Launch the GitHub Copilot app.
  3. Start the GitHub sign-in/authentication flow.
  4. Observe Opening GitHub.com to authorize....
  5. Observe that the device-code field remains - - - - - - - -.
  6. Observe Copying code to clipboard....
  7. The application remains stuck and no device code is generated.

Expected behavior

The application should generate a valid device code and complete the GitHub authentication flow.

Additional context

  • Windows 11
  • GitHub Copilot app 1.1.21
  • Copilot CLI in WSL 1.0.83 works normally
  • GitHub website is reachable from Windows
  • https://github.com/login/device opens successfully in the browser
  • Windows clipboard functionality works normally
  • The Windows app was completely removed and reinstalled, including its app-specific WebView2/application data
  • The issue reproduces after the clean reinstall
  • Screenshot attached showing the authentication screen with the missing device code

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the sign-in flow in GitHub Copilot app 1.1.21 on Windows 11 and inspect the github.exe process while it remains on the device-code screen. Compare the app’s behavior with https://github.com/login/device and the working Copilot CLI in WSL; done means a valid device code is generated and authentication completes.

Written by the indexing model from the issue text.

Assessment

Tech stack
github
Domain
authentication, desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.