After upgraded to Xcode 4.2, Organizer - SVN repository stopped working

Question

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

Answer 1

I have this same issue, with Xcode 4.2 (Build 4D199) being able to connect initially (green lights) then losing connection shortly after (red lights). But this only happens when I am connected to the same LAN as the SVN repository using a cable. If I switch to a wireless connection, Xcode is able to connect again (green lights). In all cases I am able to ping and connect to SVN using the terminal and other SVN tools. It is just Xcode that struggles. You could try going wireless or through VPN to bypass this problem.

Answer 2

1. Close Xcode and all of Subversion clients
2. Go to Keychain Access.app
3. Search for all 'svn' entries.
4. Delete all which can be related to your repository (assuming that you remember users and passes)

5. Checkout project from the command line (Terminal.app) (to be sure, I use svn which goes with Xcode in the example below, may be You have installed another svn command line from macports or sth?)

   /Developer/usr/bin/svn co  http://my-svn-pet-name:8080/... tmp-dir
   

6. Provide users and passes when svn asks for them.

7. Go to Keychain Access.app again and for newly created entry (search for svn again) in details/Access Control, give access to password for all apps (this's not needed in 99% of cases but can fix issues with svn versions and other subversion clients mismatches).
8. That's it. Xcode should see your repositories again, or after recreating shortcuts to them in Organiser.

Answer 3

I had the same problem using VisualSVN.

I could connect to is over HTTPS://mysvnserver:8443/ where I then was requested for a user/pass combo.

In Xcode the connection always failed. Sometimes Xcode would complain about the certificate not being issued by a trusted authority, which in my case would be correct.

The certificate is in my keychain as always trust but that didn't solve the issue.

My solution:

1. open an terminal window
2. type command svn co https://mysvnserver:8443
3. A request is issued for the certificate security press P to allow permanent.

Answer 4

Had the same problem. The dots are green in the list of repositories but it just refuses to commit changes or update status, though compare works fine.

I opened Repositories, then on the left pane selected the project under the repository item. In the bottom-left of the window you'll have two buttons, Update and Commit. I pressed Commit there and it worked fine. However, after that it still wouldn't commit through the project (Alt+Cmd+C or through File menu). Not sure exactly what's going on.

Answer 5

I have been having the same issues, starting with beta_7 (previous betas of 4.2 did not exhibit the issue). I upgraded to the GM of 4.2, and still the same.

I discovered what was happening in my situation. The URL endpoints I've been used are SSL (https://my-svn/etc/etc). When I logged in via Safari to test, I was being presented with the "cert might not be valid" warning, then I continued past this and was able to enter my creds and could see the repository structure (as expected).

I initially thought that the cert being used on the server had expired, and Xcode was honoring the warning behind the scenes. Next time I tried with Safari, I chose the "View Certificate" in the warning, and saw that the cert was still fresh (2018 expiration date), but that our self-signed cert was not pointing to a Certificate Authority, and Safari was reporting that my Mac did not trust that cert. So, I chose the "Always trust" options that are presented by the dialog, and the warnings went away in Safari. The "forced trust" is established in the Mac's Keychain, so then I launched Xcode and viola, all of the associated repository entries in Organizer glowed green.