为 XCode 项目设置存储库
我不小心删除了 XCode Organizer 中的存储库。我已经再次设置了存储库，但是我如何告诉项目应该使用哪个存储库，因为我收到此错误：
无法访问存储库“(null)”。
我认为在 Xcode 3 中这要容易一些。
I accidentally deleted the repository in the XCode Organizer. I've set up the repository again but how can I tell the project which one it should use because I get this error:
The repository "(null)" could not be reached.
I think it was a little bit easier in Xcode 3.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
使用管理器中存储库选项卡中的“添加工作副本...”再次设置后 - 重新启动 Xcode4。一分钟前这对我有用 Xcode 4.2
After setting it up again by using "Add working copy..." from the Repository-Tab in the Organizer - restart Xcode4. This worked for me a minute ago with Xcode 4.2
从命令行签出您的 svn 项目并删除所有 .git 文件夹。然后重新签入项目。完成此操作后，您应该能够通过 Xcode 的打开启动屏幕签出 svn 项目，并且它应该正常运行。
Checkout your svn project from the command line and remove all .git folders. Then re-check in the project. Once this is done you should be able to checkout the svn project via Xcode's opening splash screen and it should behave normally.
我以前也遇到过这个问题。 Xcode 和 svn 并不是一直都工作得很好。
我解决 Xcode/svn 问题的解决方案通常包括首先备份所有更改的文件，然后从 Xcode 中删除存储库，删除工作项目文件夹，然后重新添加存储库并再次签出项目文件夹。这给了我一份干净的工作副本。此时，我需要手动重新编辑从备份中进行更改的所有文件。
这不是解决这些问题的最快方法，但至少我了解解决方案，并且可以相当轻松地做到这一点。
如果我在执行此操作后收到“无法访问存储库（空）”错误，我发现实际重新启动 Xcode 会使问题消失。
I've had problems with this before. Xcode and svn don't work terribly nicely all the time.
My solution to fixing Xcode/svn issues that I've had usually involves firstly backing up any changed files, then removing the repository from Xcode, and deleting the working project folder, then re-adding the repository and checking out the project folder again. This give me a clean working copy. At this point then I need to go and manually re-edit any files that I've made changes in from the backups.
It's not the fastest method of fixing these issues, but at least I understand the solution, and can do it fairly easily.
In the case where I've gotten the "the repository (null) could not be reached" error after doing this, I found that actually restarting Xcode made the problem go away.