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
Source tree version 3.2.6 (Windows) not able to authenticate with Bitbucket.
While refreshing token it gives the following error. The button click does not open bitbcuket url instead open some localhost url http://localhost:34106 and show the below error message
Unable to get secret
Error Reading JObject from JsonReader. Path '', line 0, position 0
Also started having error "Error Reading JObject from JsonReader.."
Started with trying to add another github oauth account. It is mighty unclear where the oauth procedure fetches its account??? And it is not clear if you can have two different oauth definitions and if they can target the same github acount??
Why and when do you need to add the account to the repository url? There must be many ways to communicate to sourcetree what account you want to use in current session/project.
Recovered from the "Error Reading JObject" -error by opening Sourcetree options - git and scrolling down to find button "Update Embedded" and if the fully automatic installation completes without error the problem may be fixed.
Sometimes the installation ends with and error and sometimes I have had TLS errors. (Maybe randomly locked by virus protection or Windows indexing and other horrors that can lock files)
Switching to "System" based Git version and back again seems to fix installation errors and when accounts a bit messed up.
Following solution worked for me
1. Open SoureceTree Options Window (Tools > Options)
2. Go to Network Tab
3. Proxy server settings
select use default os settings
select add proxy server config to git/mercurial
Please note - I am using a proxy server and trying to authenticate with bitbucket over SSH
I have the same problem. A more detailed explanation of my symptoms: