Closed DrChat closed 1 year ago
This is a known issue in recent versions of .NET tooling, see https://github.com/dotnet/sdk/issues/22987
The workaround is to pass --verbosity minimal
on the command line to ensure the device code link and code are logged.
Thank you @JohnSchmeichel for the workaround and context. Adding --verbosity minimal
worked for me.
This issue has had no activity in 90 days. Please comment if it is not actually stale.
I wasn't prompted via dialog or command-line to enter any credentials. After 90 seconds of waiting, it exited with the above error.