I recently upgraded my Xcode to 4.2. Since then my Organizer-Repository stopped working. Initially it said \"Host is unreachable\" and placed red dot every where.
In
When you use any IP to access SVN, XCode sends local user's credentials and SVN cannot authorize user;
You just need to create an alias for your IP in hosts and use that alias in URL instead of IP. A comprehensive manual of how to make aliases you can find here. At the end my URL looked like http://svnserver:8080/svn/...
.
The problems are only with the latest XCode 4 (build 4C177 — iOS 5 beta 7).
A slightly earlier version of XCode 4 (build 4C104 — iOS 5 beta 5) works fine.
Like Saran, I tried the suggestions from majkelx and OMH and they did not work for me.
When I launch build 4C177, and immediately open the Organizer, the repositories initially show green (as Saran noted) and histories are available. Any other operation turns them red. But the comparison view in the text editor successfully shows diffs against the repository, with revision number.
So, I conclude that the repositories are set up OK and authentication is actually working, but various source-control functionality in build 4C177 is buggy. I'd advise installing an earlier XCode 4 and waiting for the next release. I filed a bug report with Apple.
After upgrading to Xcode 4.2, I had the same problems, red dots, and "host unreachable".
I tried the recipe from majkelx, but those dots where still red.
But then I just tried to check out the repository with the Xcode organizer instead of the command line. And suddenly it all worked!
(It may not have worked without fiddling with the Keychain, like majkelx described)
EDIT: When searching for Subversion entries in keychain, also seach for "sub", not just "svn". My passwords where in "subversion". Only my web subversion password was in "svn". Just one more hint for others who are struggling with this. I wasted more than an hour on this today. :-)
Tried everything, "Host is unreachable" all the way.
The following fixed it instantly for ME (using a https connection(!)):
Enter your repo address in Safari (only server address might work, as well).
When Safari warns you about trusting the server, "always accept" the certificate.
Restart Xcode. Done. Works.
Xcode 4.2's SVN is well and truly broken.
svn from the command line works just fine, so I don't see how it can be an authentication issue -- it's just a straight bug and a demonstration of how much testing Xcode releases receive these days... The Xcode 4 series has been a lot of backwards :-(
SVN in Xcode 4.1 was almost working properly.... And now it doesn't work at all. Whee!
Try remove the "https://login@" from your svn address Works for me.
for http://my-svn-pet-name:8080/
try something like my-svn-pet-name:8080/