I was using Xcode 4.3 and Subversion (SVN) for source control. Everything was working fine. I was able to see the files I've changed, compare with server version and commit.
Then Xcode 4.4 was released and I downloaded the new version and installed it. Now, source control has stopped to work. I don't see the files I've changed, and it seems that source control is not enabled.
Things I've already tried:
Delete all files from my local folder and use "Connect to repository" option on the XCode initial screen
Download everything from server with command line as I always did
Did anyone have any problem regarding source control?
I'm not sure if I'm answering your question here or a slightly different one, but I'd been searching around for an answer to a similar question - I would set up a new project in Xcode, then using svn command-line tools put it up on my svn repo; however in Xcode 4.4 (unlike its predecessors) this would not subsequently allow me to use the Xcode svn controls (my favourite being the Version editor panes).
The answer for me was to close the project, delete the project's derived data (Organizer -> Projects -> Select correct project -> Hit "Delete" button in line with "Derived Data") - then load up the project again.
Apologies if this does not in fact address your issue, but Xcode 4.4 seems to have introduced a few bugs regarding source control so perhaps this will assist in some way.
Support for using Source Control in xcode is mostly aimed at new/fresh starts in xCode. Aligning existing projects with the changes is less well explained. I found this partly helpful http://asciiwwdc.com/2013/sessions/414 but ponderous. Muddling on gave the best result.
Related
I'm using Xcode 8.3.3 with SVN. I'm able to connect to an existing repository, make changes, and check in my code. However, It looks like the branching menu items are missing.
I have configured Trunk, Tag, and Branches options; and then was given the option to add branches. But after creating the branch, no changes seem to have been made.
Expected menu (from a training video):
Actual menu (from my project):
Note: "mobile" is the name of the working folder.
SVN is still fully supported in XCode 8.3.
The issue I was having above was that the code was not properly matched to the repository location. When the developer clicks "Check Out..." they are presented with the option below. The developer must map to the branch folder.
As an aside, SVN branching support removed in XCode 9.0. To work around this, the developer can have both versions of XCode installed - switch back to 8.3 (or older) to manage SVN branches.
XCode 5.0.1 on OSX 10.9 does not show the full revision history for my repository under Source Control/History.
What it does display is the history up to a certain point several months ago, but nothing newer than that.
I tried viewing the repo and its history in Versions and there it works just fine.
At some point we migrated the repo from one server to another. We also upgraded the repository a while back, but I don't know to which version of SVN. However, I do know that we have Visual SVN Server and SVN 1.8.0 serverside.
On the other hand, the XCode 5.0 release notes state that XCode uses SVN 1.7, which leads me to suspect that this could be the cause of my issue. However, I also seem to remember that XCode used to refuse to work with unsupported versions of SVN.
Any ideas what could be causing the problem?
What sucks, but is the default in Xcode is that the server status is not automatically updated.
Open the preferences and go to the Source Control Preference and make sure the "Refresh server status automatically" button is checked.
There is nothing I can find within the Xcode UI besides this that tells you the server history is current or how to refresh it.
This is verified as of Xcode 5.1.1. What a shitty UI. Really.
Cheers.
In my case sometimes begins work after "Source Control/Update".
Actually, its terrible bug, you have no guarantees that you see actual list!!!
To answer my own question, it appears that there was something wrong with the working copy. Deleting it and then doing another checkout directly from XCode fixed the problem.
Yet another variation on 'turn it off, then on again'.
My team is using GitHub with Xcode. We use the GitHub application for OS X to commit, branch and sync. The problem is that when two or more developers add files to the project, conflicts occur in the 'project.pbxproj' file. Recently I realized there is a commit/push/pull option in Xcode.
If I stop using the GitHub application and use Xcode's commit, push, pull and merge, would those conflicts in 'project.pbxproj' file stop occurring?
You can still have conflicts.
If somebody makes a change to the project file and you make a change to the project file and you try to commit it at the same time as (or soon after) the other person, there's a good chance you'll see conflicts.
Thankfully, the "project.pbxproj" project file is text which can you can open with your favorite editor (vi or emacs or whatever) and you can resolve the conflicts rather easily.
I have a large Xcode project for a game I'm building. I recently switched versions of the animation framework I'm using (cocos2d), and to keep things clean, I went ahead and created a brand new Xcode project from scratch.
Afer creating the new project file, I made copies of all my source files in the filesystem, then symlinked them into the new project by dragging them into the Xcode Project Navigator. Everything worked fine.
But here's where it gets weird. Whenever I use the Xcode Search Navigator to do global text searches on my project, it searches files from the old project! And only files from the old project!
The only conceivable explanation I can come up with is that Xcode is somehow recognizing my filenames as being the same as were used in the old project, and has decided to ignore the newer versions in favor of the old ones. Is there any such cache or preference within Xcode that can do such a thing? Keep in mind the paths are different, since the new project's files all exist in a brand new directory. But the class names are the same.
In case this is relevant: I once created an Xcode Workspace that included the old version of this project (but not the new one.) I abandoned the workspace long ago as it was problematic, in favor of working with the project directly.
UPDATE: This appears to be an Xcode-related problem-- I have discovered I have the same lack of search-ability in all of my projects. I uninstalled Xcode (I had the version that was still using the Developer directory) and installed the latest version (4.3.3) that does not use the developer directory, but I am still seeing this problem.
I am curious if anyone knows a way to wipe out Xcode's cache of project code indexes, if such a thing exists, that might potentially "reset" its knowledge of my projects and thus fix the situation. Possibly something in the Library directory?
One last clue as to what might be happening: In addition to the search navigator failures, I noticed one of my projects was still using resources that no longer existed in the filesystem-- again, making me think Xcode has cached information about my projects somewhere and is now using outdated versions of my files that no longer exist. this post helped me solve that problem by resetting the simulator's content and settings, but the search issue persists.
Have you checked your Find Options? This same problem was biting me and then I remembered I had added a custom Scope in 'My Scope' that directed XCode to my other project. Changing this back to 'Workspace' fixed the problem.
Is there are means whereby if files are altered outside of Xcode, that a warning in can be shown to ask if you want to refresh the file? This feature is available in Visual Studio, for example.
As a temporary solution, were working on source files in a Dropbox folder.
Although growl notifies us that some files has changed, Xcode doesn't know about these changes.
No, Xcode won't do that, and since there's no support for plugins you're pretty much stuck with that behavior. Some suggestions:
Create a local git repository (Xcode can do this for you when you create the project, I don't know if you can do it once it is created.
Use another IDE, like AppCode (this isn't even a solution, just came to me and I decided to add it).
With a version control system you can see the little 'M' on edited files, browse changes, etc. But since you wrote that this is a temporary solution I bet you already know this.