NuGet VS17 sporadically fails connecting to VSO/VSTS feeds - VS Bug 365798 #4365

Closed
nkolev92 opened this Issue Jan 23, 2017 · 4 comments

Comments

Projects
None yet
2 participants
@nkolev92
Member

nkolev92 commented Jan 23, 2017

Dup of VS: Bug 365798
VS 2017 sporadically has trouble connecting to VSO feeds.
VS version: VS 15.0.0-RC3+26117.0.d15rel at least and later

The issue is sometimes resolved by random restart/clean cache.

Playing around with the entering/not entering credentials when prompted I managed to get it

@nkolev92 nkolev92 self-assigned this Jan 23, 2017

@nkolev92 nkolev92 added this to the 4.0 RTM milestone Jan 23, 2017

@nkolev92 nkolev92 added the Area: Auth label Jan 23, 2017

@nkolev92 nkolev92 changed the title from NuGet VS17 sporadically fails connecting to VSO feeds to NuGet VS17 sporadically fails connecting to VSO feeds - VS Bug 365798 Jan 23, 2017

@nkolev92

This comment has been minimized.

Show comment
Hide comment
@nkolev92

nkolev92 Jan 23, 2017

Member

Steps to a possible repro:

  1. Launch VS
  2. Auth VS user
  3. Create project
  4. Add dependency from a VSO feed
  5. Log out from VS
  6. Close VS
  7. clear the cache ex. "NuGet.exe locals all -clear"
  8. Launch VS and open project (not Auth'ed)
  9. Do "Restore NuGet Packages" before doing a "Manage Nuget Packages"
  10. Open "Manage NuGet Packages" and you should not get prompted to auth.

And we're in the above mentioned scenario.

Everything seems fine, if the user does "Manage NuGet Packages" before doing a restore though.
So that might be a workaround for now.

The problem with this repro is that it's not a normal user scenario to log in/log out of VS frequently. While this is an issue it's likely to be the root cause of the reports

Member

nkolev92 commented Jan 23, 2017

Steps to a possible repro:

  1. Launch VS
  2. Auth VS user
  3. Create project
  4. Add dependency from a VSO feed
  5. Log out from VS
  6. Close VS
  7. clear the cache ex. "NuGet.exe locals all -clear"
  8. Launch VS and open project (not Auth'ed)
  9. Do "Restore NuGet Packages" before doing a "Manage Nuget Packages"
  10. Open "Manage NuGet Packages" and you should not get prompted to auth.

And we're in the above mentioned scenario.

Everything seems fine, if the user does "Manage NuGet Packages" before doing a restore though.
So that might be a workaround for now.

The problem with this repro is that it's not a normal user scenario to log in/log out of VS frequently. While this is an issue it's likely to be the root cause of the reports

@nkolev92

This comment has been minimized.

Show comment
Hide comment
@nkolev92

nkolev92 Jan 23, 2017

Member

And here's a workaround that worked for me in a couple of test cases.

  1. Log out from VS.
  2. Close VS.
  3. Launch VS and Auth.
  4. Close VS.
  5. Do a "NuGet.exe locals all -clear"
  6. Launch VS
  7. Open your solution
  8. Do a "Manage NuGet Packages"

Note: If you have a Net.Core project make sure to turn off Auto Restore before Step 4

That should fix it.

Member

nkolev92 commented Jan 23, 2017

And here's a workaround that worked for me in a couple of test cases.

  1. Log out from VS.
  2. Close VS.
  3. Launch VS and Auth.
  4. Close VS.
  5. Do a "NuGet.exe locals all -clear"
  6. Launch VS
  7. Open your solution
  8. Do a "Manage NuGet Packages"

Note: If you have a Net.Core project make sure to turn off Auto Restore before Step 4

That should fix it.

@nkolev92

This comment has been minimized.

Show comment
Hide comment
@nkolev92

nkolev92 Jan 23, 2017

Member

The issue is reproducible on VS.25019, prior to RC1.
Not an RC3 regression.

Member

nkolev92 commented Jan 23, 2017

The issue is reproducible on VS.25019, prior to RC1.
Not an RC3 regression.

@rrelyea

This comment has been minimized.

Show comment
Hide comment
@rrelyea

rrelyea Feb 3, 2017

Contributor

How is fix progressing? Should we balance due to your v3 vsix work today?

Contributor

rrelyea commented Feb 3, 2017

How is fix progressing? Should we balance due to your v3 vsix work today?

@rrelyea rrelyea changed the title from NuGet VS17 sporadically fails connecting to VSO feeds - VS Bug 365798 to NuGet VS17 sporadically fails connecting to VSO/VSTS feeds - VS Bug 365798 Feb 9, 2017

@rrelyea rrelyea added the Regression label Aug 15, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment