You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I'm trying to hunt down an issue with Bitbucket integration with Visual Studio 2019, and I'm trying to determine if the recent break is related to the Bitbucket HTTPS removal on March 1st, or related to the newest versions of Visual Studio 2019 (16.11.11) and Git (2.35.1). The issue also persists in the newest versions of Visual Studio 2017 and Visual Studio 2022.
I have always used Bitbucket with SSH and MFA without issues since last summer so I wouldn't think that that the updates on March 1st would have affected me. Also, connection to my Bitbucket repos worked in Visual Studio through March 9th, right before I updated to the newest versions of Visual Studio 2017 and 2019.
It seems as though this issue is on Visual Studio's end as I was still able to interact with Bitbucket through Windows Terminal, but I still want to make sure that Bitbucket supports the newest version of Git (2.35.1). Does it? According to this page you should, but nothing explicit is stated. If I can rule out any issues on the Bitbucket side I can focus my attempts to fix this on the Visual Studio front.
Here is a link to my post on the Visual Studio Community Forums for more information if you'd like to see. It's been six days and no word from Microsoft so my hopes are getting dim on that front.
Visual Studio Professional 16.11.11 Breaks Git SSH Access - Visual Studio Feedback
I forgot to mention I did read through this post as well:
Can not log in to Bitbucket in Visual Studio (atlassian.com)
But since the announcement states "this does not impact those using an SSH key to authenticate with Git." I did not think it would affect me since I've always used a SSH key to access my Bitbucket repositories.
Hi @Frank Ceci and welcome the community.
We haven't seen any issues with Bitbucket Cloud and the latest version of Git.
I believe that the user who mentioned that version 2.35 of Git does not work with their version of BitBucket may be using Bitbucket Server instead of Cloud, as they are referring to a version of Bitbucket (which we don't have in Cloud). See also the feature request here for Bitbucket Server to support Git 2.35: https://jira.atlassian.com/browse/BSERV-13114
If you can interact with your Bitbucket Cloud repos from a command-line tool using Git 2.35, but the same operations (e.g. clone, pull, push) are failing from Visual Studio, then the issue seems to be specific to Visual Studio (it may be a configuration issue or a bug).
You are very welcome, it's good to hear that it is being looked into and I hope it gets resolved soon.
Please feel free to reach out if you ever need anything else!
With VS 2022 the plugin does not work and there is no answer from ATLASSIAN for getting this features as supported by Github's VS plugin: GitHub Extension for Visual Studio - Visual Studio Marketplace
I think this is a really bad situation for teams using Visual Studio for development.
I created an issue here to bring attention / upvote
I was told in the Visual Studio forums listed above that Bitbucket does not support Git 2.35, and the newest versions of Visual Studio released in March use Git 2.35. That seems to be the case after my testing. When I downgraded Visual Studio to previous working version and then uninstalled and reinstalled Git, I used the newest version of Git which was 2.35.1. That didn't work. Then downgrading Git fixed the issue.
For reference I am now using Visual Studio 2019 16.11.10 and Git 2.34.1, which are the latest versions of both that will work.
If this is in fact the case, can you guys update your documentation page? What version of Git do you support? | Bitbucket Cloud | Atlassian Support
I will wait to hear back from someone on the Atlassian team before marking this as an answer.