DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Newsletter
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • Java Developers, Don't Throw Out Your Mac Yet: Apple Will Contribute To OpenJDK
  • 7 Great Terminal/CLI Tools Not Everyone Knows

Trending

  • Idempotency Under Concurrency: Why Your Application Check Isn't the Last Line of Defense
  • Build Software Faster With Three Simple Principles
  • Building a Practical Cloud-Native Golden Path: A Guide to Kubernetes-Based Service Delivery, Self-Service, and Developer-Friendly Defaults
  • Detection and Response Did Its Job. Now Someone Has to Actually Fix It.

Draft This article hasn't been published, so readers can't see it.

In moderation This article is waiting for review, so readers can't see it yet.

Deleted This article has been deleted, so readers can't see it.

Git's SourceTree in Mac OS X and Resolving Error 69

Opening SourceTree in Git generates error 69, which occurs after the application XCode has been updated, but not yet opened.

By 
Venkatt Guhesan
·
Oct. 03, 15 · Code Snippet
Post on X (opens in a new tab) Share on LinkedIn (opens in a new tab)
5.3K Views

Join the DZone community Save articles, join the discussion, and download Refcards and Trend Reports with a free account.

Join for free Already a member? Log in

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:

The message means that you need to open XCode and, since, it hasn’t run since the last update, you need to accept the new EULA agreement that’s part of the updated XCode. Once you accept the license, close XCode, then go back to the other application that was throwing the error.

Mac OS X

Published at DZone with permission of Venkatt Guhesan. See the original article here.

Opinions expressed by DZone contributors are their own.

Related

  • Java Developers, Don't Throw Out Your Mac Yet: Apple Will Contribute To OpenJDK
  • 7 Great Terminal/CLI Tools Not Everyone Knows

Partner Resources

×

Comments

Loading comments

The comments didn't load

Please try again in a moment.

Likes

Loading

The next likes didn't load. Please try again.

The likes didn't load

Please try again in a moment.

See who liked this

Log in or join DZone for free to see who liked this article.

Log in Join for free
  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook