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'.
Related
I am trying to figure out how to open an old version of my Xcode project that is stored in GitLab. Usually, I use Xcode to push updates to Gitlab and on the occasions, I've had to get my project from GitLab, I simply click the "Open in Xcode" button on GitLab, which brings my project up.
The problem that I'm having now is that I've accidentally introduced a bug into the project that crashes the app and I can't figure out how to crush this bug. The last couple of updates to GitLab contain this bug so I need to revert to a copy a bit in the past. When I click on this update, there is no open in Xcode button, and I'm unsure about how to open this previous version.
I'm hoping that there is a straightforward solution to getting this old version of this file up. I'm just getting started using git, and I'm hoping someone on here can provide some insight.
Can someone please point me in the right direction on the easiest way to revert to an old project update on GitLab?
It seems easier to:
close XCode
cd /path/to/local/clone/of/GitLab/repo
switch to the command line and type git switch <old SHA1> in order to update the working tree with the files content of that past SHA1
open XCode back up.
(Note: git switch is better than the old legacy git checkout command)
If you want to commit some fixes, your git switch command will be:
git switch -c fix <old SHA1>
That will start a fix branch starting from <old SHA1>.
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.
I created a project with local git repository using XCode 5 (preview 6), made some changes and tried to commit, and finally got the message "The repository 'HelloWorld2' could not be reached, please verify that the repository is online and reachable and try again".
The same message is also shown when the Refresh Status menu item under Source Control menu is clicked.
Actually, I have XCode 4.5 installed and run side by side with 5.0, but the issue does not exist when the project is opened using Xcode 4.5. Also, the commit action works fine as well via command line.
Not sure if this helps in the tracking down of this problem, but here goes anyway:
I have been connecting to a local network git repository perfectly well for a number of months, but I encountered this problem later yesterday and nothing I did seemed to improve the situation. That included:
Rebooting both the development machine and the server;
Reinstalling Xcode from the App Store;
Re-cloning the project from the git command line (which could see the repository perfectly well);
Checking out the repository from Xcode (I was able to check out but every other operation, such as , Commit, Refresh Status etc. seemed to cause the problem...)
Manipulation the repository with SourceTree (which could also see it fine).
Eventually I stumbled across a solution to my local issue. If I launch Xcode with a wired and wireless network enabled then I can't see the repository. If I close it, disable wifi and relaunch it then I can.
I've not had much opportunity to work out what the difference is (especially as the wifi connects to the same network and is the secondary choice for networking) but it does seem to fix it.
Hope that might help others and hopefully I can find a real explanation soon!
Dave,
Lion, Xcode 4.3.3, and vex code 4.5 dp4
After creating a new local git branch to specifically avoid this type of problem, I'm unable to open a critical production workspace with xcode 4.3.3 after having opened it, in another branch, with xcode 4.5pd4. I also tried cloning from origin again, as I haven't pushed to remote since opening the workspace in 4.5, but I'm unable to open that version of the workspace either. No matter what I do, Xcode 4.3.3 crashes soon after launching. What can I do to reset, delete preferences, whatever, to get 4.3.3 working again?
Submitting this for completion purposes
I had to have inadvertently opened the workspace on the incorrect branch at one point; it's the only thing that makes sense. I noticed that after opening it under 4.5 again, all my xib's were defaulted to an incorrect compatibility in IB, and after manually adjusting them all to proper values using the current tools versions and making sure none were set to use a new, feature (that I'm not naming here due to NDA purposes) I was once again able to open the workspace under both 4.3.3 and 4.4.
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.