允许多台 Mac 处理同一个 iOS 项目
我需要知道如何让 2 台 Mac 处理同一个项目。
目前该应用程序位于应用程序商店中，并且只有 1 台 Mac 正在运行该应用程序。 我想向项目添加一个新的开发人员，即新的 mac。
请向我提供完成这项工作所需的简单、分步说明（关于证书、钥匙链、捆绑包等）。
PS该应用程序也使用推送通知，新的Mac会损坏推送通知机制吗？
我遇到了在多台Mac上开发iPhone应用程序，它并没有真正回答我的问题。我想知道，从 Apple 的角度来看，我需要在新的 mac 上做什么才能从两台机器构建完全相同的可执行文件。 （并且不会损害当前的推送机制）。
谢谢...
I need to know how to allow 2 Macs to work on the same project.
Currently the app is in the app-store and only 1 mac is working on the app.
I want to add a new developer, i.e. new mac, to the project.
Please provide me with a simple, step by step, instructions I need to do in order to make this work (regarding certificate, key-chain, bundle, etc).
P.S.The app uses push-notifications as well, does a new mac will damage the push notification mechanism?
I came across Developing iPhone app on multiple Macs, it didn't really answer my question. I want to know, from Apple perspective, what do I need to do in the new mac in order to build the exact same executable from both machines. (and not harm the current push mechanism).
Thanks...
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
有一个工具叫做版本控制。您可以使用 git、SVN 或 Mercurial。
编译时（使用您公司的 Apple 开发人员帐户），您的代码在两台 Mac 上将是相同的（如果您在两侧都进行了更新）。实际上，我自己的代码是在我的 iMac、我的 Mac Book Air 或我女朋友的 Mac Book Pro 上无差别地编译的。
There is a tool called version control. You could use git or SVN or Mercurial.
When compiling (with your company Apple Developer account) your code will be identical on both Mac (if you updated on both sides). Actually, my own code is indifferently compiled on my iMac, my Mac Book Air or my girlfriend's Mac Book Pro.
确保第二台 Mac 安装了相同的 iOS 开发工具和 SDK。从第一台 Mac 导出您的开发人员和分发证书。在第二台 Mac 上创建一个新的用户帐户并在那里安装证书。将您的项目和所有源文件（包括应用程序的 plist、xib、资源等）复制到第二台 Mac（或者，如果您使用版本控制存储库，请查看所需修订版本的新副本）。
推送通知与用于构建应用程序的 Mac 无关。如果第一台 Mac 充当推送通知服务器，它仍然可以为第二台上构建的应用程序执行此操作（只要您不更改任何 ID 等）
Make sure the 2nd Mac has the same iOS Development tools and SDK installed. Export your Developer and Distribution certificates from the first Mac. Create a new User account on the 2nd Mac and install the certificates there. Copy your project and all source files ( including the app's plist, xibs, resources, etc.) to the 2nd Mac (or, if you are using a version control repository, check out a fresh copy of the desired revision).
Push notification have nothing to do with the Mac used for building an app. If the 1st Mac is acting as the push notification server, it can still do so for apps built on the 2nd (as long as you don't change any IDs, etc.)
版本控制:) http://en.wikipedia.org/wiki/Revision_control
基本上，你有一个存储开发中文件的通用框（称为“存储库”）
此存储库具有一些功能，例如版本回滚、冲突和修改跟踪、错误跟踪等...
这个想法很简单：您拥有您的文件和在线文件存储库，您添加那些文件到您的存储库。然后，我加入该项目并获取这些文件（操作称为“签出”），修改其中一堆文件，然后执行一项称为提交的操作：此操作检查我的版本，将修改后的文件与在线版本合并。然后，您“更新”您的本地版本：如果您没有修改我所做的相同行，则不会出现错误，并且您会成功更新。如果我们修改同一行，并且存在冲突，更新过程就会中断。然后您可以看到错误出现的位置，并使用 diff 工具解决它（http://en.wikipedia.org/wiki/Diff）
作为概念非常简单，对于我们开发人员来说非常基础。您可以让多少人从事同一个项目而不会出现问题。您可以处理单独的代码，而不需要其他代码。您可以处理同一个文件而不会产生冲突。
<一href="http://www.google.com/url?sa=t&source=web&cd=1&ved=0CCcQFjAA&url=http://code.google.com/&rct=j&q =去ogle%20code&ei=RGpnTvrIC4_LtAbqzanxCg&usg=AFQjCNFHgvJ0hYT3isyCVFQucmLRlUCw2Q&sig2=nxZtos7brQUVzOFghhEtrw&cad=rja" rel="nofollow">Google 托管 和 Sourceforge 是两个很好的存储库示例（您可能还想查看 Git 有点不同）
所以，简单地说：SVN 就是您需要的答案:)
versioning :) http://en.wikipedia.org/wiki/Revision_control
basically, you have a common box where to store your in-developement files (called "repository")
this repository has some features like version rollbacking, conflict and modifies tracking, bug tracking and so on...
the idea is simple: you have your files and your online repository, you add those files to your repo. i then join the project and grab those files (operation is called "checkout"), modify a bunch of them and i perform an operation called commit: this operation checks my version merge the modified files with the one online. You then "update" your local version: if you didn't modify the same lines i did, there's no error and you succesfully update. If we modified the same line, and there's conflict, the update process breaks. You can then see where the error appears, and resolve it with a diff tool (http://en.wikipedia.org/wiki/Diff)
Pretty easy as concept, pretty fundamental for us developer. You can have how many people working on the same project without problems. You can work on separate bits of code without the need of the other. You can work on the same file without generating conflicts.
Google hosting and Sourceforge are two great example of repositories (you may also want to check out Git which a little bit different)
so, briefly: SVN is the answer you need :)