Xcode 4.2 can't commit code by svn?

I have the exact same issue with Xcode 4.2 and Lion 10.7.2.

I am unable to perform any svn operation from Xcode because I get the error mentioned by Jason, however I can successfully commit or update my project from the Organizer.

Calin

Same problem here. Same symptoms. Everything works nicely from the command line though.

The only difference is that I'm running on Snow Leopard. So it's definitely a problem with Xcode 4.2, not the OS.

UPDATE: It looks like Xcode 4.2 *DOES* work with Svn in some cases, since my Xcode install is able to access a friend's SVN repo. However, I'm at a loss as to why it won't connect to my repo. Both repos are using HTTPS and SVN server 1.6.

AFAICT, the only difference is that my friend's repo has a signed/authorized SSL sertificate and my own repo is merely self-signed....?

I have the latest 4.2 running on 10.7.2

now organizer cannot reach my repositories but I can reach some on the web

deleted and recreated mine same problem (it will be briefly green before turning back to red)

deleted entry matching svn or sub in keychain same problem

both of the above still same problem.

If I use the svn cli everything is fine, I can commit, update, etc... without any problem.

the snv in on a 10.6 server, it is version 1.6.16 (r1073529).

The 10.6 server has only a self sign certificate if this has any matter

Looks like the developers having this problem are using self-signed SSL certificates for their SVN servers. I've filed 10294665 with Apple's online rdar bug reporter.

@ShinySteelRobot

This is not entirely true.

I am using the svn:// protocol, and when I try to update or commit my project from Xcode I get the "Repository could not be reached" error. However, from Organizer, I am able to successfully commit or update the project.

I do have another smaller problem when trying to update, I have to click Update twice because the first time it says that the project is up to date.

I will fill in a bug report with Apple also.

Thanks for everything you did on this issue.

the 'good' thing in all that is:

the cli still works fine

for now back to the good old terminal with svn update and commit.🙂

Getting burned by this as well. That said I've found a workaround using XCode 4 to check files back in to svn.

Instead of using the Project Navigator, use the Organizer:

1. Choose the folder containing the project you checked out of your svn repository.
2. At the bottom of the Organizer window, click on the "Commit" icon.
3. Select the files you want to check in and add your comment.

I have the exact same issue with Xcode 4.2 and Lion 10.7.2.

Apple is aware of the issue/bug.

As i said before, For me:

Via Xcode it does not work.

Via organiser it does not work since what ever I do/try my repositories are red.

As I said before, back to the good old cli for now. Of course the draw back is you have to cd to your project first or type the full path and the svn small icons in Xcode do not get updated since my repositories are off line as far xcode is concerned.

Of course it is an inconvenience to loose the integrated 'gui' svn, but eh Life goes on

Any idea to deal this problem?

Short answer: Wait for Apple's fix.

If it is practical or/and worth it. You could use external svn if they work fine or if it is ssl issue by a proper certificate for your server, but all these might cost money and time.

Do waht I do, use the good old cli svn update and commit and if you want some gui I use svnx. I agree it is not integrated within xcode but it does the job in the meantime.

append "domain name" in etc/hosts file.

ex> 192.168.0.100 repos.mysvn.com

add repository again. uising domain name.

ex> http://repos.mysvn.com/repos/

checkout again.

It did not make any contribution to the issue.

And the subversin source control was bother.

BTW: Sorry for my poor english.

Open Safari, navigate to your online repo.

When it will complain against self-signed SSL, click view certificate, then check Allways trust...

You will be prompted for keychain access, comply.

Restart Xcode, your repo should be online.

😉