I am having trouble connecting my project repository to XCode, ever since I've upgraded to 4.2. I have a local server with a forwarded port to be accessed from outside the local network. I have a DNS record pointing to the external ip. When I explicitly define the external ip (i.e https://123.456.789.000/svn/...) the repository is properly linked, no problems. This also works when I specify the internal address. The issue is when I use the repository dns - XCode shows a red dot with "Host Unreachable". I am sure this is an XCode 4.2 specific issue, because I tried this in other clients, including older XCode versions. The basic problem is - the external DNS doesn't work with https. Any ideas? Thank you!

8 Answers
8

Open your svn web address in Safari (not any other browser) - using the dns name

It should come up saying the address is untrusted as the cert is a different name / address

Click show certificate and then tick the box saying always trust then continue

it may prompt you for your mac username / password to add to the keychain

Open xcode and try again using the DNS name..

The issue with xcode and accessing svn servers which have HTTPS certificates which fail any of the checks (be it host matching, self signed etc..). Opening the addresses in safari and adding as trusted solves this problem!

You could also use the command: svn list https://mysvnserver.com/ if you want to do the checkout from Xcode instead. This method this method worked for me, but accepting the certificate in safari didn't work.
–
Rn222Jan 25 '12 at 14:43

Worked for me too, but since the certificate was renewed, I had to delete an old stored information from the ~/.subversion/auth/svn.ssl.server/ directory. Before, even with (p) entered svn asked every time again (and XCode didn't accept/work).
–
robbashMay 18 '12 at 7:50

1

I had the same issue. This one helped but had to run as sudo
–
GeorgeMay 10 '13 at 9:14

This is an XCode 4.2 issue and you are just going to have to wait for an update from Apple or go back to a previous version. While these links (which you've probably already read) may not solve the problem, it may at least give you further information

Thanks Joel, I will keep looking into a possible workaround until the bounty expires. If indeed there is no way to achieve this, I will mark your answer
–
StavashOct 30 '11 at 13:39

I wish it were the simple but I was able to resolve it but simply using the HTTP protocol and forcing re-authentication. Worked like a charm after several days of hair pulling.
–
D3vtr0nJun 20 '12 at 22:59

Hi chown, thank you for your answer. I put in these details and the repository does appear to be linked with a green indicator, but once I want to do a checkout, I see no files / revisions.
–
StavashOct 30 '11 at 7:51

Hmm, maybe this doesnt work then. I was hopeing xcode would recognize ssl by the port number (and not just httpS) but I guess not. Sorry @stavash, Ill play around with this more and see if I can get it working because I just noticed this happening on one of my old project repo's as well.
–
chownOct 31 '11 at 18:46

This worked for me. HTTP somehow cleared out the HTTPS settings and re-authenticated. Worked like a charm, thanks.
–
D3vtr0nJun 20 '12 at 23:02

What about just navigating in a terminal window to ~/Documents/[projectname] and doing the svn commit from there? You should get prompted to accept the cert.

Perhaps Xcode does some things behind the scenes that make this a bad idea? I just don't know if there is any difference between doing your commits within Xcode (i.e. File > Source Control > Commit) or just doing it from the command line. I've done both before and haven't noticed any problems.