search

microsoft / azure-repos-vscode

Azure Repos extension for VS Code
Other
661 stars 451 forks source link

TFVC Source Control Viewlet Sync Error - (team) You are signed out. Please run the 'team signin' command. #476

Closed gmrscott closed 4 years ago

gmrscott commented 5 years ago

Steps to reproduce

  1. Connect to an Azure DevOps Services Repo via the Team: Signin command and the Authenticate and get an access token automatically (new experience) option.

  2. Open the local TFVC Repository folder of a team project and verify that Azure Repos detects the project by the fact that the indicator changes from Team (i) to the project's name.

  3. Open the TFVC Source Control Viewlet and verify that you are able to see all included and excluded changes.

  4. Inside the viewlet, click the '...' Menu followed by the Sync option.

  5. In the bottom right corner, you will see the following error notification: (team) You are signed out. Please run the 'team signin' command.

I receive this error every single time I try to Sync. If I am unable to pull down my team members' changes, this extension becomes darn near completely useless for me and my team.

Any thoughts?


Technical Details

Visual Studio Code

Version: 1.30.2 (system setup) Commit: 61122f88f0bf01e2ac16bdb9e1bc4571755f5bd8 Date: 2019-01-07T22:54:13.295Z Electron: 2.0.12 Chrome: 61.0.3163.100 Node.js: 8.9.3 V8: 6.1.534.41 OS: Windows_NT x64 10.0.17134

Azure Repos Extension

Version: v1.144.1 (2018-11-05)

filippoitaliano commented 5 years ago

Same problem.

Technical Details

Version: 1.31.0 (user setup) Commit: 7c66f58312b48ed8ca4e387ebd9ffe9605332caa Date: 2019-02-05T22:35:56.624Z Electron: 3.1.2 Chrome: 66.0.3359.181 Node.js: 10.2.0 V8: 6.6.346.32 OS: Windows_NT x64 10.0.17134

Azure Repos Extension

Version: v1.144.1 (2018-11-05)

jurual commented 5 years ago

Same problem, since installing Visual Studio 2019 preview

borjapuerta commented 5 years ago

Same problem with VSCode: Error message: Unauthorized. Check your authentication credentials and try again.

VSCode Versión: 1.31.0 (user setup) Azure Repos Extension Version: v1.144.1

I have Visual Studio 2017 installed at my computer.

filippoitaliano commented 5 years ago

The problem is related to some change inside vscode@1.31. https://github.com/Microsoft/azure-repos-vscode/issues/477

A workaround is to install vscode@1.30 https://code.visualstudio.com/updates/v1_30 and disable auto update for now https://stackoverflow.com/questions/50162685/how-do-i-disable-vs-code-of-updating-itself

ewaschenko commented 5 years ago

Can't login, getting the error

Unauthorized. Check your auth credentials and try again.

Happened as soon as I updated to 1.31.0

gmrscott commented 5 years ago

The problem is related to some change inside vscode@1.31. https://github.com/Microsoft/azure-repos-vscode/issues/477l

A workaround is to install vscode@1.30 https://code.visualstudio.com/updates/v1_30 and disable auto update for now https://stackoverflow.com/questions/50162685/how-do-i-disable-vs-code-of-updating-itself

I am the OP and in the Technical Details portion of my post, you can see that the version where I experienced this issue was in fact 1.30.2.

dragoljub commented 5 years ago

I downgraded to VS Code 1.30.0: https://update.code.visualstudio.com/1.30.0/win32-x64-user/stable and now am able to connect to TFS with Azure Repos 1.144.1. Win 10 Enterprise.

filippoitaliano commented 5 years ago

@gmrscott Sorry, you're right. This is strange, I'm now using vscode@1.30.2 and it works as usual. I experienced the issue updating from 1.30.2 to 1.31.

RCKSTR1 commented 5 years ago

Happening to me too. Just after the January update :(

I'm running VSCode Jan2019 update and TEE-CLC-14.134.0 + The Azure Repos extension on macOS High Sierra 10.13.6

I'm able to do get and checkin on the terminal, but not with the extension.

mdschweda commented 5 years ago

Same problem here

Version: 1.31.0 (system setup)
Commit: 7c66f58312b48ed8ca4e387ebd9ffe9605332caa
Date: 2019-02-05T22:35:56.624Z
Electron: 3.1.2
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 10.0.17763

TFS 15.117.27414.0 (Tfs2017.Update3)
TF.exe 15.129.28306.1
beyerleinf commented 5 years ago

Same Problem with the current insider build

Version: 1.32.0-insider
Commit: d049558486b5ccebc607c826ac4055970b0bc80e
Date: 2019-02-11T06:13:08.554Z
Electron: 3.1.3
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Linux x64 4.9.0-8-amd64
HackproTm commented 5 years ago

Same problem

Version: 1.31.0 (system setup) Commit: 7c66f58312b48ed8ca4e387ebd9ffe9605332caa Date: 2019-02-05T22:35:56.624Z Electron: 3.1.2 Chrome: 66.0.3359.181 Node.js: 10.2.0 V8: 6.6.346.32 OS: Windows_NT x64 6.3.9600

admir86 commented 5 years ago

not resolved in 1.31.1

Version: 1.31.1 (user setup) Commit: 1b8e8302e405050205e69b59abb3559592bb9e60 Date: 2019-02-12T02:20:54.427Z Electron: 3.1.2 Chrome: 66.0.3359.181 Node.js: 10.2.0 V8: 6.6.346.32 OS: Windows_NT x64 10.0.15063

reinisbz commented 5 years ago

Same problem.

Version: 1.31.1 (user setup) Commit: 1b8e8302e405050205e69b59abb3559592bb9e60 Date: 2019-02-12T02:20:54.427Z Electron: 3.1.2 Chrome: 66.0.3359.181 Node.js: 10.2.0 V8: 6.6.346.32 OS: Windows_NT x64 10.0.16299

dragoljub commented 5 years ago

Can someone on the latest version try changing the extension proxy settings to see if it fixes the issue for you?

image

Larhei commented 5 years ago

@dragoljub Yes it fixes the issue for me on Mac latest VS Code Version

beyerleinf commented 5 years ago

@dragoljub This fix also works for the latest stable and insiders build! Thanks! :)

chrmarti commented 5 years ago

This should be fixed in current insiders builds of VS Code with the Proxy Support setting set to 'override'. Let me know if you still see any issues with that. Download: https://code.visualstudio.com/insiders/

filippoitaliano commented 5 years ago

Is the issue fixed in https://code.visualstudio.com/updates/v1_32? I didn't tried yet.

chrmarti commented 5 years ago

This should be fixed in 1.32 if you do not have a network proxy configured for the TFVC server.

If you do have a network proxy configured, you can try unsetting it by adding the TFVC server to the NO_PROXY environment variable and giving the latest 1.33 Insiders build a try: https://code.visualstudio.com/insiders/ (feature request: https://github.com/Microsoft/vscode/issues/68260)

Let me know if that helps.

filippoitaliano commented 5 years ago

Thanks! I don't have a network proxy configured for TFVC and the 1.32 works perfectly.

onelifenyc commented 4 years ago

Version: 1.47.2 (user setup) Commit: 17299e413d5590b14ab0340ea477cdd86ff13daf Date: 2020-07-15T18:22:06.216Z Electron: 7.3.2 Chrome: 78.0.3904.130 Node.js: 12.8.1 V8: 7.8.279.23-electron.0 OS: Windows_NT x64 10.0.18362

Can someone help out - this started happening recently. See GIF.

(ISSUE: "Exclude" and it gets added back. Also, after that even DIFF would not work and keep prompting me to run 'team signin' but I am signed-in just fine)

issue with vscode and azure repos ext

dragoljub commented 4 years ago

I’m seeing similar issues through my company VPN. Sometimes when I click on a pending change it takes 3 rounds of asking me to sign in. I just keep clicking until the diff finally shows up. I don’t actually have to sign in more than once. TFVC Win 10 latest VS code x64.

dragoljub commented 4 years ago

I'm actually seeing this same thing now. It seems like TFVC plugin is logging in and out in a loop over and over.