MyThinkPond

On Java, Python, Groovy, Grails, Spring, Node.js, Linux, Arduino, ARM, Embedded Devices & Web

  • Recent Posts

    September 2015
    M T W T F S S
    « Aug   Dec »
     123456
    78910111213
    14151617181920
    21222324252627
    282930  
  • Subscribe Options

  • Awards

    JavaCodeGeeks
  • Most Valuable Blogger @ DZone
  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 173 other followers

  • Follow MyThinkPond on WordPress.com
  • Blog Stats

    • 364,698 hits
  • General Options

Solved: git status failed with code 69 error when opening SourceTree in Mac OS X

Posted by Venkatt Guhesan on September 24, 2015

If you receive the following error when opening SourceTree or other applications installed in your Mac OS X, then here is how you can solve it. Sometimes people make things more cryptic than it needs to be.

Error encountered

‘git status’ failed with code 69:’

Agreeing to the Xcode/iOS license requires admin privileges, please re-run as root via sudo.

and here is the example of the screenshot:

2015-09-24_14-50-56

Solution:

What that message is telling you is that you need to open the application XCode on your Mac OS X and since it hasn’t run since the last update, you need to accept the new license EULA agreement that’s part of the updated XCode. Once you accept the license and close the XCode application and then go back to your other application that was throwing the error and try opening it. The error no longer happens.

Cheers

Advertisements

2 Responses to “Solved: git status failed with code 69 error when opening SourceTree in Mac OS X”

  1. Algen said

    Hello,

    I can’t find any contact info in the site so forgive me for using the comment section. I’m Algen, I work with engineering website EEWeb.com and would love to have your website featured as a site of the day on EEWeb. Is this of interest to you?

    Hope to hear from you soon.

    Sincerely,

    Algen

  2. zakir said

    Thank @Venkatt Guhesan, my issue resolved by following your steps

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

 
%d bloggers like this: