Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,460,395
Community Members
 
Community Events
176
Community Groups

SourceTree 2.5.3 reverts to 2.5.1

I have a really strange issue going on here on macOS Sierra 10.12.5.

After many, many failed attempts to upgrade SourceTree 2.5.1 to 2.5.3 when prompted by the automated update process (downloads successfully and appears to update successfully but version remains at 2.5.1 when the app restarts), I decided to download the 2.5.3c version from the website and install the new version that way. I have tried both overwriting the 2.5.1 version and deleting 2.5.1 before moving 2.5.3 into my Applications directory. SourceTree appears to remain at 2.5.3 until I restart my Mac, but when I launch SourceTree, I'm back at 2.5.1.

Any idea what might be going on?

1 comment

Mystery solved. It turns out it was a combination of my own stupidity and launching the application from Spotlight.

Somehow I had multiple installs of SourceTree, one in /Applications (2.5.3) and another in ~/Applications (2.5.1). When I would launch SourceTree from Spotlight, it was launching the one in my home directory Applications. Doh!

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events