Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7071011
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 28, 20262026-05-28T05:38:08+00:00 2026-05-28T05:38:08+00:00

I just got a new Mac (with Lion) and am setting everything up, but

  • 0

I just got a new Mac (with Lion) and am setting everything up, but I am stuck on this SVN certificate trust error for my repositories on Assembla.

The most common solution seems to be to move to Terminal and perform some svn operation on my working copy there, then respond to permanently trust the certificate when prompted.

Here is where I am stuck. With the Terminal, I never get a certificate trust prompt! I can happily list, commit, check out a new copy, anything, no problem. With svnX, again, no problem . Neither way am I ever prompted to trust the certificate.

But, with XCode 4.2 or Coda, I get stuck on the certificate trust error. I’ve tried removing anything in the keychain related to svn or assembla, doesn’t help. I’ve tried browing to my repository in Safari, and again I can log in and am never given a certificate prompt.

I am utterly baffled. If anyone has any ideas, please help! Thanks!

Coda gives me this:
svn: OPTIONS of ‘https://subversion.assembla.com/svn/my/repo/path’: Server certificate verification failed: issuer is not trusted (https://subversion.assembla.com)

And XCode gives me this:

Error validating server certificate for 'https://subversion.assembla.com:443':
 - The certificate is not issued by a trusted authority. Use the
   fingerprint to validate the certificate manually!
Certificate information:
 - Hostname: *.assembla.com
 - Valid: from Thu, 24 Mar 2011 19:30:40 GMT until Sun, 24 Mar 2013 19:30:40 GMT
 - Issuer: 07969287, http://certificates.godaddy.com/repository, GoDaddy.com, Inc., Scottsdale, Arizona, US
 - Fingerprint: ae:b0:b6:94:14:5f:4b:28:d2:82:68:ae:e9:18:85:b3:ea:36:ee:f2
(R)eject, accept (t)emporarily or accept (p)ermanently? 
svn: OPTIONS of 'https://myuserid@subversion.assembla.com/svn/my/repo/path': Server
 certificate verification failed: issuer is not trusted (https://subversion.assembla.com)
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-28T05:38:08+00:00Added an answer on May 28, 2026 at 5:38 am

    You need to make sure you use the svn binary in the Developer Tools package. If you go to the directory under version control and type

    /Developer/usr/bin/svn up
    

    You should be prompted to accept the cert, press p to accept permanently and then xcode should work.

    On newer versions of XCode 4 which come as an appbundle, try this instead:

    /Applications/Xcode.app/Contents/Developer/usr/bin/svn up
    

    If the Xcode appbundle is elsewhere, just edit the path accordingly.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I am new to programming but had some spare time and just got a
I'm new to C programming and I just came across this program and got
I am new to mac os x programming and just got an assignment to
Just got a brand new mac. However when I try to install netbeans 7.0.1,
We just got new servers for our new system and I want to know
Just got the new iPad, and when I touch the microphone and say a
I've just got the new Visual Studio 2010 Ultimate and Javascript Intellisense is not
I have an existing application (with MySQL DB). I just got a new requirement
I just got myself a new toy, a phone with Windows Mobile 6. I'm
I just got a shiny, brand-new Debian server handed to me by our Systems

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.