-
Notifications
You must be signed in to change notification settings - Fork 710
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
"dotnet restore --interactive" in WSL fails (does not pop up UI) #549
Comments
@EranGon - we need more of the [CredentialProvider] logs to investigate further. Mainly, we need which authentication flow it was attempting to use. Did it fall through to device code flow, and you want to use browser auth? If so, you need to set There was a stale issue that was closed about WSL using the windows context. Please comment on this issue to reopen if this is the case: #461 |
@embetten here's the required logs.
|
After more investigation, it appeared that the issue was a result of network connectivity issues in my WSL. |
Transferred from NuGet/Home#14169. Provided by @EranGon
NuGet Product Used
dotnet.exe
Product Version
9.0.103
Worked before?
Yes, but not sure what was the version
Impact
I'm unable to use this version
Repro Steps & Context
The symptoms
In WSL, when running "dotnet restore --interactive", no UI pops up, and restoring fails.
The only errors I get are these:
/usr/lib/dotnet/sdk/9.0.103/NuGet.targets(170,5): warning : [CredentialProvider]Warning: Cannot persist Microsoft authentication token cache securely!
/usr/lib/dotnet/sdk/9.0.103/NuGet.targets(170,5): warning : [CredentialProvider]Warning: Using plain-text fallback token cache
To Reproduce
Any .NET 8 project
WSL with Ubuntu distro version 22.04.5 LTS
dotnet version 9.0.103
Feed is hosted in Azure DevOps artifacts
Verbose Logs
The text was updated successfully, but these errors were encountered: