This update has totally crippled my operations. I've spent hours trying to get Bitbucket and Sourcetree to work. I have a ton of updates I need to push but am always getting logged out and blocked from pushing or fetching. Total nightmare. Will probably have to look at other GIT options to resolve this.
Our azure devops build server can't connect anymore. I can't configure it to connect to bitbucket... I guess we'll have to migrate our git on Azure... Thanks Bitbucket.
@Thomas Samuel If you're just using the command line for git, all you should need to do is create an app password and use that password instead of your normal one, nothing else would be different.
I've been trying to resolve this issue for like two days to no avail. How do I push my code from my local directory to the remote directory. I've followed almost all the suggestions listed in the comment sections and still stuck. I keep getting stuffs like the below:
remote: The requested repository either does not exist or you do not have access. If you believe this repository exists and you have access, make sure you're authenticated. fatal: repository 'https://bitbucket.org/chuzzy1/workspace/projects/WEB/' not found
Note: I have created the App Password and I have two repositories on my account. I even tried deleting the repositories to start afresh but the prompt says it'll take up to 30 days before it could be effected. I just need an easier way to push code from my local directory to the online repo via the terminal.
With auto-generated App Passwords you have made use of Bitbucket very difficult. The amount of friction you have added is crazy. To have App Passwords separate from account password - that's fine. Besides auto generated password you need to allow users to pick their own passwords.
I create a pass.txt file to copy my autogenerated passoword. Terrible practice I know, so you need to do something so people don't resort to such bad practices. Help!
Who approved this? This for me is so much friction that I consider moving to Github or Gitlab.
PS. How about autogenerating passwords for bitbucket accounts. People are terrible at choosing their passwords. Sarcasm.
VS Code git integration doesn't seem to store the password for very long. So if I don't store autogenerated password locally in a file, once I need to enter the password, what I'll do is to go to bitbucket App Password and keep generating a new password each time. Usually generate one new password per day. Friction. Friction.
This is total mess. So long article solving nothing. I need quick solution. How to access to my source over HTTPS after your changes. In GitHub is simple, you just need to create token and use token. Could you put instructions in few steps how to replace account credentials with some new credentials and to access to source with HTTPS?
Just discovering this after failing to be able to push local changes to my repository.
Is there an 'easy to follow' and intelligible work around for that because the proposed solution in that article and in received email are totally cryptic to me. I only want to code and share my code to others, I don't care about cryptography and security.
How many times am I going to have to fix this? This is the 3rd time it has stopped working after I've spent hours getting it working again. How much time do you really expect people to waste attempting to fix this Atlassian?
The App password setup is a bit unobvious and have major ux issues.
When you configure you app password, it's not an access with a specific identifier, it is still to be used with your main account identifier / username (not appname).
So when you configure your "app" password in Source tree, you have no idea what app password it is using because there is no hint (and app password is obviously hidden).
Similarly, in Bitbucket you cannot see the rights that where assigned to the App password making it pretty much impossible to use and validate (to reuse or debug).
I hate it, I have a successful app password authenticated yet I still cannot fetch or pull from my branch and all that happens is it tells me that it no longer supports bitbucket passwords. However, I did not use a bitbucket password, I used the app password created in atlassian. You were the chosen one Anakin, you were supposed to destroy VS git not join them.
Oh, for Heaven's sake guys...I JUST created a NEW APP PASSWORD last Friday and got it working for the 3rd time and yet again, ONE WEEK later, it tells me I don't have credentials. All I did was close SourceTree a week ago and open it today. WHY DOES IT KEEP BREAKING???
I cannot get over this, why change it? It asks me once a week for my app password that was shown to me once. I learned the first time and saved it to a file which is way less secure that just using my own password. Still it won't let me pull 2 commits that I did at home - putting in the app password will successfully authenticate and then I just get the same damn error message.. VS git won't let me pull without pushing the metadata files that it uses. It's absolutely awful right now.
283 comments