Skip to content
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

--interactive switch not displaying device flow in version '6.0.100-preview.7.21379.14' #11202

Closed
wli3 opened this issue Aug 30, 2021 · 4 comments
Assignees
Labels

Comments

@wli3
Copy link

wli3 commented Aug 30, 2021


Issue moved from dotnet/sdk#20332


From @fuocor on Wednesday, August 25, 2021 3:23:17 PM

dotnet restore --interactive or dotnet tool restore --interactive is not outputting the device flow information for authenticating.

it hangs for the 90 second timeout to elapse.

downgrading the global.json file to '5.0.300' works

@wli3
Copy link
Author

wli3 commented Aug 30, 2021


Issue moved from dotnet/sdk#20332


From @MihaZupan on Monday, August 30, 2021 3:01:01 PM

cc: @wli3

@wli3
Copy link
Author

wli3 commented Aug 30, 2021


Issue moved from dotnet/sdk#20332

  • Please respond to @dotnet-issue-labeler[bot].

From @dotnet-issue-labeler[bot] on Monday, August 30, 2021 6:58:54 PM

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

@erdembayar
Copy link
Contributor

erdembayar commented Sep 11, 2021

@fuocor
I was not able to repro this issue, for me it restore finished successfully after some waiting.
Please note if required packages are already in your global packages cache then it may not try to connect authenticated source feed?

First I cleared my local cache:
dotnet nuget locals all -c

image

Also once your cred provider already cached auth details then it doesn't trigger device flow in next try.
image

Could you tell me which cred provider are you using?
Could you be able to provide log from dotnet restore --interactive --verbosity detailed?

@erdembayar erdembayar added the WaitingForCustomer Applied when a NuGet triage person needs more info from the OP label Sep 11, 2021
@aortiz-msft
Copy link
Contributor

We were not able to repro the issue with the Azure Artifacts Credential Provider installed; hence, closing this bug. Please feel free to comment with more information.

@ghost ghost removed the WaitingForCustomer Applied when a NuGet triage person needs more info from the OP label Sep 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants