XCode 4 (Assembla) SVN Repository “Unable to load

问题:

I've been trying unsuccessfully to connect to an https assembla svn repository with the new xcode 4 IDE for an iPhone project I'm working on.

I was able to connect just fine with the last version of xcode (3?), and with other svn apps. I'm using the same repo address and credentials, so I'm baffled as to why this doesn't work.

I also tried loading in a working copy of the repo, and it cannot connect either.

The one error message that comes up is "Unable to load revisions"

Any tips?

回答1:

There are a lot of links, but no solution posted directly here, so I'll do it.

The reason Xcode4 does this is that it tries to log you into the SVN server with your mac credentials. When that fails, it basically just hangs and fails. The best solution I've seen so far is this:

open a terminal

If you don't have the project out do this:

>svn checkout SERVER_PATH FOLDER_PATH_TO_PUT_THE_PROJECT

It will then ask you for password for the mac username, you just write anything or nothing and press enter.

it will then fail and ask you for a username. Enter the correct one and then the password when it asks.

The project will be checked out, but you can just close the terminal window and delete the folder again if you want. Xcode4 will now connect without a hitch. :)

回答2:

Try this: http://forum.assembla.com/forums/2-Subversion/topics/2881-SVN-don-t-remember-my-credentials#post_9172

This helps me with same issue

回答3:

I experienced the same problem when opening a project I had previously checked out using another SVN client (Versions). So I fired up Wireshark to look at the SVN traffic and saw that it was an HTTP authentication problem.

I opened up the Xcode Organizer window (Shift-⌘-2) and deleted the autogenerated repository bookmarks. Then I added my own fresh bookmark. That fixed it.

You could also try deleting the repository bookmark in the organizer and just reopen the project. That seemed to work for another of my projects. It asked me for my password and everything started working.

And don't forget to tell the organizer the paths to trunk, branches and tags. It can't guess those from a local checkout, and setting them up will enable you to do branching, merging and tagging from within Xcode 4.

It is probably worth noting that Xcode 4 crashed on me about 5 times during this process. I think it is still early days for the new and improved SCM integration. So good luck!

回答4:

See this post: xcode 4 with subversion SVN server–Tips TYVM InteractiveWebs! Xcode4 and SVN are playing nicely together once again.

回答5:

Solution found! I followed the instructions on the page, and it cleared up all my issues: http://plainoldstan.blogspot.com/2011/03/xcode-4svn-could-not-authenticate-to.html

Essentially, it seems that Subversion or Xcode was caching a wrong username/password combo.

回答6:

I had a similar problem; was working in XCode 3 blah blah...

I followed all the instructions here and here but still it was hanging.

The problem was that my svn username and my mac OS username and password were the same. Once I'd changed the name of my svn user it worked!

Hope this prevents anyone else spending a day's work on this

回答7:

There is another change in xcode 4 that can contribute to svn connectivity problems and that is that the name lookup for host names only uses a dns lookup and will not see any hosts in the /etc/host file. This impacts more than svn connectivity. An example is in the iphone simulator if you are attempting to connect to a local (not in dns but in the /etc/host file) system you will not be able to see it. This would imply that issues around name lookup would impact other areas like git … The workaround is very gross you must use ip addresses in the URI. Unfortunately the xcode team decided it would be unimportant to surface this information either in the docs or in some type of error log or message. A simple test is if you can ping the host but nslookup cannot find it then xcode will also not be able to see it.

回答8:

I resolved this issue simply replacing the IP address with the NetBios name.