git-ecosystem / git-ecosystem/git-credential-manager
Cannot render authentication prompt UI on Windows-arm64
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 9.3k
- Forks
- 2.9k
- Avg merge
- 7d 1h
- Merged PRs (30d)
- 14
Description
Version
2.4.1
Operating system
Windows
OS version or distribution
Windows 11 Pro Arm 64
Git hosting provider(s)
Azure DevOps
Other hosting provider
No response
(Azure DevOps only) What format is your remote URL?
None
Can you access the remote repository directly in the browser?
Yes, I can access the repository
Expected behavior
There are 2 expected behaviors that are not happening.
- There should be no auth prompt in the first place. I have the following GCM config set:
[credential]
interactive = auto
azreposCredentialType = oauth
msauthUseBroker = true
msauthUseDefaultAccount = true
as well as
[credential "azrepos:org/<ORG>"]
username = me@contoso.com
azureAuthority = <AUTHORITY_URL>
On this same machine, in this same state https://aka.ms/azureauth doesn't need to prompt and uses the current OS account without issue.
- GCM is launching an auth prompt, and that prompt should render an allow me to continue with the auth flow.
Actual behavior
- Silent auth via broker isn't happening.
- The prompt renders an empty window frame. The program icon is shown on the task bar, and the window frame outline is there, but the body is transparent and empty.
Logs
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the empty authentication prompt and missing silent broker authentication on Windows 11 ARM64 with GCM 2.4.1, using the configuration and Azure DevOps setup described here. Compare the prompt rendering and broker behavior with the expected OAuth flow; done means silent authentication works or the prompt renders usable authentication controls.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp
- Domain
- authentication, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100