Extension for Visual studio unknown error - unable to push or fetch anything
I reported this as a bug since it just started happening to me right after updating to 15.7.6.
Reason: The same error message was when GitHub deprecated support for TLS1.0 and TLS1.1 some months ago. And now it looks like Atlassian made some changes to BitBucket's networking on 06-Aug-18 (https://blog.bitbucket.org/2018/08/06/update-ip-migration/). This change could be related to the problem.
Workaround: The bundled Git-Credential-Manager-for-Windows in Visual Studio 2017 is not of the latest release yet. Downloading the latest release and putting it on top of the files in Visual Studio 2017 fix the issue:
- Download the zip file gcmw-v1.16.3.zip from https://github.com/Microsoft/Git-Credential-Manager-for-Windows/releases
- Navigate to C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer\Git\mingw32\libexec\ (or wherever your 'missing' git-askpass.exe resides)
- Make a backup copy of the git-core folder
- Put the files from the zip file on top of the contents of your new git-core folder and overwrite where prompted
Also seems you need to remove "login" from remote settings if such is configured (i.e change https://[email protected]/myrepo/myproject.git to https://bitbucket.org/myrepo/myproject.git) and use Atlassian ID with full email instead.
For now, I'm just setting my pass on my 'git clone url' and that solved my problem.
I'm still looking for a better solution, though.
It seems to affect some Visual Studio users since a few hours ago, even with no changes taken place in the environment prior to that. Something apparently went wrong in Git integration with Visual Studio.
There is currently a workaround, where you set the password in the remotes settings of the repository, as shown here, but note that it is insecure as it requires storing the password in plain text.
Another workaround is to work with Git using command line.
A third workaround, which I also find the best one, is to configure SSH key authentication. As of now, it seems to work with Visual Studio 2017 without any issues. This is the solution I chose.