Xcode control commit commit error

Question

I am trying to transfer my Xcode project to server based SVN. I configured it, open the "Source Control" window and click the "Lock" button. It is a bit chunks and then gives me an error: the working copy of "xxx" could not commit the files. Failed to contact assistive application.

What is a helper application ???

I saw similar posts for GIT, but they don't seem relevant (or at least not enough information for me) to work with SVN.

Answer 1

There seems to be a bug in Xcode 7 that you may or may not encounter: when creating a new project with the Git repository, Xcode 7 may cause it to “fail to communicate with the helper application”. The same error can tell you that it "cannot transfer files."

This happened to me after upgrading from Xcode 6.x, which Ive never had this problem with.

It turns out that the “helper application” is actually Git: for some reason, Xcode 7 wants to associate you (the committer) with a name and email address. Xcode even offers access to Mac contacts on first launch.

To fix this, all we need to do is launch our reliable Terminal application (command line tool) and tell Xcode who we are, and these errors are a thing of the past. The good news is that this should happen only once. Here's how to do it:

At the command prompt, enter the following:

xcrun git config --global user.email [e-mail] xcrun git config --global user.name "Your Name Here" 

Answer 2

Today I faced the same problem. And I open the terminal:

 cd [project path] svn commit -m "your log information" 

then you will see the specific causes of the error. Then I solve the problem according to the error. Therefore, it is best to add and delete files through Xcode in order to correctly update svn status (and not Finder).

In case of a commit error, go to the command line and use svn status to get a hint about what's wrong and fix it from the command line.

Answer 3

This morning I had the same problem while I was making code using Xcode 7.2

Xcode could not contact helper application

I just open the same project in Xcode 6.4 and it was a successful commit.

Answer 4

Today I faced the same problem - all of a sudden, after SVN commits worked fine for a while (Xcode 7.3). It seems that SVN integration is minimized, including meaningful error messages. I think that the error returned from the svn command-line tool (which is an auxiliary application in this case) is handled in a general way.

So, in my case, it turned out that I added some files to my Xcode project through Finder, added them later to Xcode via "Add Files ...", and again deleted one of them through finder. I noticed that this file was annotated using "A!". I called svn status from the command line and saw a file annotated with "M!"

After svn revert <filename> and svn delete <filename> I could transfer other files using Xcode.

It is best to add and delete files through Xcode in order to correctly update svn status. In case of a commit error, go to the command line and use svn status to get a hint about what is wrong and fix it from the command line.