Xcode Git issues with Google Drive/Dropbox

Apparently XCode should recognize a git repo automatically, but after doing git init and my initial commit, XCode is not seeing the repo. I have my entire project and git repo in Google Drive, and I suspect that is causing some issue? What do I have to do to get XCode to read .git files in Google Drive?


  • Any Git shortcuts for the current branch and the branch it tracks?
  • override merge two branches in Git
  • Should we ignore Solution Output folder while we are using Visual Studio and Version Control?
  • Git when used with Mac and Windows simultaneously gives unnecessary conflicts
  • Sourcetree: how to revert a git pull
  • Add all visual studio projects to GitHub and sync them through SkyDrive
  • I tried doing a git init, add and commit to a project in my local drive and XCode still didn’t recognize the git store, so this may not be a G Drive/Dropbox issue.

  • Git - working on wrong branch - how to copy changes to existing topic branch
  • Problems using maven with git
  • How to create a CocoaPod with nested git submodules?
  • Diff between Simulink models .slx
  • Export a local git
  • How can I do a git clone operation using Cake
  • One Solution collect form web for “Xcode Git issues with Google Drive/Dropbox”

    Don’t put a Git repo on Dropbox or Google Drive. It is terrible. Dropbox, on sync, can scramble all git’s internal files and screw it up your whole repository.

    Instead, use a Git service. For something private, I recommend BitBucket.


    Imagine you put your main repository on Dropbox. You sync your dropbox in another computer and pushes to it. The connection drops from that computer. You go to other computer, make another commit and pushes into the main repository. Everything goes fine.

    Dropbox starts to sync in this computer. At the same time, the other computer starts to sync, too. But internally, there are lots of different files on the repo. How Dropbox knows how to keep and organize these files?

    Simple answer: it doesn’t. It will damage your repository, and that’s nothing you can do about it. And this is not some kind of “it will almost never happen”. It will happen, very soon.

    And about the real question:

    I never used Xcode, but I had similar issues with Eclipse. It’s simple, though: Xcode does not know about the repo because you did not tell him that is a repo. To see how to do that on Xcode, you could see here.

    Git Baby is a git and github fan, let's start git clone.