SVN certificate trust error with XCode 4.2 or Coda, but not with command-line or svnX

xcode svn xcode4.2 coda
dms-dc picture dms-dc · Dec 11, 2011 · Viewed 9.6k times · Source

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://[email protected]/svn/my/repo/path': Server
 certificate verification failed: issuer is not trusted (https://subversion.assembla.com)

Answer

mjmdavis picture mjmdavis · Jan 17, 2012

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.

Related questions

How to merge conflicts (file project.pbxproj) in Xcode use svn?

There are two members in our team. We use Xcode's SCM (use SVN) to manger our source code files. We all add files to our Xcode project. He has committed to SVN server. When I update, Xcode find there has …

Read More
What does the Subversion status symbol "~" mean?

I am getting a tilde symbol when I do an svn status. Here is the output of the project after editing it in XCode. svn status M build/Currency_Converter.build/Currency_Converter.pbxindex/imports.pbxbtree M build/Currency_Converter.…

Read More
Using Subversion with DropBox

Is it a bad idea to use DropBox as a backup system for Subversion repositories? Has anyone tried using Subversion with an an online file sharing utility like DropBox? What's your experiences? My concern is whether this will work - …

Read More