![]() ![]() I also tried reverting to 2.6.3 (134) and that seems to partially solved the issue. I also tried completely uninstalling the application and deleting both ~/Library/Application Support/SourceTree and ~/Library/Preferences/* and then reinstalling again with no success. I have deleted all passwords from Ke圜hain Access with no success. I have tried using the Beta version 2.7.1 (155) and the issue still persisted. The second one is BitBucket Server version 5.7.1 which I connect to via HTTPS protocol (and the url for this one is actually ). The first one is BitBucket Server version 4.7.1 which I connect to via HTTPS protocol (actually the url is just ). I have two different BitBucket Servers to which I am connecting. I am having similar issue with version 2.7.1 (159) on MacOS 10.12.6. I did not erase passwords in keychain, unlock keychain, save to keychain, use command line once, uninstall or re-install sourcetree - I just changed the git to command line git (and restarted sourcetree just because). This has resolved the issue of sourcetree repeatedly asking me for my password and having the input of a valid password not working. I "resolve" the sourcetree shenanigans by going to the preferences for git and selecting to use the system git (even if it's the same version). This is and always has been the case for me. ![]() In the comments here, there are posts that say that the command line git works. Somehow, they are not behaving the same with regards to at least authentication.Īgain, this is an assumption here, and I will test with the next set of sourcetree updates, but I think when an update or a certain level of update for sourcetree comes out - the setting for which git to use gets cleared or (re)set to internal git. ![]() Let's say internal is 2.15.1 - but my system one is 2.15.1. MY assumption of what's going on here is that somehow the sourcetree internal git is fubared in some way. I didn't read all the comments - if this has already been said, I apologize for the duplication. Reporting that you "have the same issue" and that you're running "the latest OS X" is just as bad as a "+1" in GitHub. Use the upvote button to promote useful and helpful posts. However, Community is a very different product and we would really benefit from some communication - even if the prognosis is bleakĪlso, the latest beta `2.7.2 (161)` managed to break basic auth, which was working well for me, as well as the primary issue here, OAuth.Īnyone else on this thread - don't upgrade to the latest beta when prompted.Īlso - Everyone, remember that this IS NOT a JIRA issue. I think we have a lot of us in this thread are heavy JIRA users, and are commenting in this community post like we would a JIRA issue - trying to help. can you share any updates? This community discussion has gotten out of hand without any real answers or updates.Unless I'm mistaken, this issue relates to the following two SRCTREE issues: Using the terminal allows me to push, but I don't use SourceTree for the terminal.īest solution seems to be using basic auth with an `app password` from bitbucket. I am on MacOS and this error did not happen to me before the newest update. I originally made my account with Google sign-in, then added a password to my account since the error told me to do so. I enter the guaranteed correct password and then get this error and do not push to master as desired. This error is given when I attempt to push to master on the SourceTree GUI after asked for my password. If you log in via a third party service you must ensure you have an account password set in your account profile. 12:01:52.841 git-credential-sourcetree Password encryption failed - key to to encrypt password is unavailable (nil) 12:01:52.841 git-credential-sourcetree Error generating password due to missing uuid. one or more parameters required to renew token is nil. 12:01:45.246 git-credential-sourcetree Something went wrong. 12:01:45.244 git-credential-sourcetree Error generating password due to missing uuid. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |