Xcode: "The working copy ____ has uncommitted changes" vs. git status: "nothing to commit, working directory clean"

Question

In Xcode 5.0.2, I try to pull from a remote and am given the following message:

"The working copy 'project-name' has uncommitted changes. Commit or discard the changes and try again."

Fair enough. I pull up the commit dialog, and am then given the message, "This file does not exist at the requested revision." Clicking 'OK' brings me on into the commit dialog. (There is no revision displayed in the right pane, presumably for the same reason I was given the most recent message.) Selecting the flat view, I see that there is only one modified file: project.pbxproj. I enter a commit message and click 'Commit 1 File'. When I then go to pull, I find that I am in exactly the same position as before--the same messages appear and I am unable to pull (or push) no matter how many times I make a commit.

Curious, I run git diff to see just what has changed. Nothing. git status provides me with equally helpful output: nothing to commit, working directory clean. git push or git pull? Yep, those work just fine from the command line.

So what gives? Why does Xcode insist that I have changes in my working directory? Why won't it tell me what they are? Have tried restarting Xcode and system. While I'm happy that I still have some way to push and pull, it would be really nice if the Xcode git integration was behaving nicely. Any ideas?

I've found these similar questions, but none address this particular issue (or provide an acceptable solution):

Would a `git reset --hard` help? (if you don't have any private file in your working tree) — VonC, Jan 07 '14 at 14:25
I'm suffering with this exact same problem on Xcode 5 too. I wish there was a way to resolve this. I need to switch back to a local branch to continue development. — Robert J. Clegg, Jan 15 '14 at 11:26
Try the `-f` flag for "force", for example `git checkout -f master` — turingtested, Jun 15 '22 at 07:25

Robert J. Clegg · Answer 1 · 2014-05-04T05:48:37.640

76

Okay, so I fixed my issue.

With Xcode open:

Open terminal - cd / to your project directory.
Type in: "git reset --hard"
Type in git status

Restart Xcode and make a commit (Just a comment or something )

Repeat the above steps.

This sorted out my issue for me.

edited May 04 '14 at 05:48

answered Jan 15 '14 at 11:32

Robert J. Clegg

7,231
9
47
99

Thanks, @Tander. As suggested up in the comments on the question, however, that doesn't fix my problem... – GarlicFries Jan 15 '14 at 15:11
2

In my case, the "git reset --hard" step was sufficient to fix the issue. Thank you @Tander – Kqtr Sep 14 '18 at 11:28
6

No problem @Kqtr - surprisingly, 4 years later and this is still and issue in the latest version of Xcode. – Robert J. Clegg Sep 14 '18 at 15:39
Every time I clicked something in Xcode it changed my userdata file, so I had to `git reset --hard` after every move to the unstashing action. In hindsight, maybe I only needed to do the reset right before unstashing, but for everyone else's awareness, changing views in Xcode or clicking on UI will refresh your IDE and update your userdata file. – Heinous Games May 23 '20 at 18:10

score 8 · Answer 2 · answered Jul 17 '14 at 20:19

You must fix it with command line git. Go to your working folder in Terminal, type:

git status

That will show you what files have uncommitted changes. Crashlytics, for instance, will update itself as soon as you run it, and even using Xcode/Source Control/Discard Changes won't get rid of it.

Once you see the files that have uncommitted changes (ignore added files), use:

git checkout -- Folder/filename.ext

That's the same as a "discard" in Xcode.

After you've done that, go back to Xcode and you should be able to switch branches.

score 3 · Answer 3 · answered May 20 '19 at 21:27

3

xCode is really-really crappy. Everytime you just look at files, a file called UserInterfaceState.xcuserstate is changed. You don't see it in the overview of xCode itself, through the command line you can.

Quick fix:

Open Terminal
CD to your project directory, and type the following:
git add .
git commit -m "Commit"
git push origin master

answered May 20 '19 at 21:27

J. Doe

12,159
9
60
114

How can we exclude the file? – JCutting8 Jan 24 '22 at 07:20
@JCutting8 Idk, i should not recommend it, maybe your UI is gone than – J. Doe Jan 24 '22 at 20:50

score 0 · Answer 4 · answered Jan 17 '17 at 22:27

0

App Code solution:

Confirm git status in Terminal:

git status
Open 'yourProject.xcworkspace' in App Code
VCS > Git > Branches...
Remote Branches > yourBranch > Checkout as new local branch
Confirm fix via Terminal:

git status

answered Jan 17 '17 at 22:27

Tr0yJ

3,274
1
22
30

score 0 · Answer 5 · answered May 03 '22 at 14:15

0

Try this:

Step 1:

git rm --cached ProjectName.xcodeproj/project.xcworkspace/xcuserdata/username.xcuserdatad/UserInterfaceState.xcuserstate

Step 2:

git commit -m "Removed file that shouldn't be tracked"

answered May 03 '22 at 14:15

Youssof. K.

7
4

score 0 · Answer 6 · answered Jul 18 '22 at 21:17

The top answer did not work for me unfortunately because I had untracked git files.

To fix this, go to your working folder in Terminal, type: git status

That will show you files that are not being tracked by git. Now add each file with:

git add <file with location>

You should be able to copy/pasta the file with location from what gets printed out from git status.

Xcode: "The working copy ____ has uncommitted changes" vs. git status: "nothing to commit, working directory clean"

6 Answers6

Linked