I have submitted an iPhone app to Apple for approval and distribution.
我已经向苹果提交了一款iPhone应用程序以供审批和发布。
What do I need to save of the code and compilations to be able to bug-fix if (when?) the bugs come in? Should I just save everything, or just the symbols file?
我需要保存哪些代码和编译器才能修复bug ?我应该保存所有东西，还是只保存符号文件?
2 个解决方案
#1
0
I check the all the source code and the resources needed to build the app into a source code repository (with an appropriate tag) as soon as I submit an app build. In addition I zip and backup the .dSYM directory in my build/Distribution-iphoneos directory, just in case something changes in my tool environment.
一旦提交了应用程序构建，我就会检查将应用程序构建为源代码库(使用适当的标记)所需的所有源代码和资源。此外，我在构建/分发-iphoneos目录中压缩并备份. dsym目录，以防工具环境发生变化。
Having an exact source snapshot allows me to do things such as insert NSLog statements, etc., while trying to replicate the problem, if that helps narrow down a problem source (and then reverting if not), instead of just looking at (symbolicated) crash dumps.
拥有一个精确的源快照可以让我在尝试复制问题的同时做一些事情，比如插入NSLog语句等等，如果这有助于缩小问题源的范围(如果不是的话，则恢复)，而不是只查看(符号化的)崩溃转储。
#2
3
to decipher possible crash reports with symbolicatecrash tool you'll need to store symbols file.
要理解可能的崩溃报告，您需要存储符号文件。
Whether or not store other things is up to you I think, it may depend on what application updates do you plan to make. For example you may be still developing some new features and release an update with just hot bug fixes - in that case you need a separate branch in your source control for that. If you plan to ship an update that does not differ from your dev version separate branches may be not necessary.
我认为，是否存储其他内容取决于您，这可能取决于您计划进行哪些应用程序更新。例如，您可能还在开发一些新特性，并发布一个更新，只对热bug进行了修复——在这种情况下，您需要在源代码控制中使用一个单独的分支。如果您计划发布与开发版本不同的更新，则可能不需要单独的分支。
But I personally make separate tag in svn with actual code used for each appstore submission - may be it is not always useful, but it certainly won't hurt.
但是我个人在svn中使用每个appstore提交的实际代码创建了单独的标记——可能它并不总是有用，但肯定不会有什么坏处。
#1
0
I check the all the source code and the resources needed to build the app into a source code repository (with an appropriate tag) as soon as I submit an app build. In addition I zip and backup the .dSYM directory in my build/Distribution-iphoneos directory, just in case something changes in my tool environment.
一旦提交了应用程序构建，我就会检查将应用程序构建为源代码库(使用适当的标记)所需的所有源代码和资源。此外，我在构建/分发-iphoneos目录中压缩并备份. dsym目录，以防工具环境发生变化。
Having an exact source snapshot allows me to do things such as insert NSLog statements, etc., while trying to replicate the problem, if that helps narrow down a problem source (and then reverting if not), instead of just looking at (symbolicated) crash dumps.
拥有一个精确的源快照可以让我在尝试复制问题的同时做一些事情，比如插入NSLog语句等等，如果这有助于缩小问题源的范围(如果不是的话，则恢复)，而不是只查看(符号化的)崩溃转储。
#2
3
to decipher possible crash reports with symbolicatecrash tool you'll need to store symbols file.
要理解可能的崩溃报告，您需要存储符号文件。
Whether or not store other things is up to you I think, it may depend on what application updates do you plan to make. For example you may be still developing some new features and release an update with just hot bug fixes - in that case you need a separate branch in your source control for that. If you plan to ship an update that does not differ from your dev version separate branches may be not necessary.
我认为，是否存储其他内容取决于您，这可能取决于您计划进行哪些应用程序更新。例如，您可能还在开发一些新特性，并发布一个更新，只对热bug进行了修复——在这种情况下，您需要在源代码控制中使用一个单独的分支。如果您计划发布与开发版本不同的更新，则可能不需要单独的分支。
But I personally make separate tag in svn with actual code used for each appstore submission - may be it is not always useful, but it certainly won't hurt.
但是我个人在svn中使用每个appstore提交的实际代码创建了单独的标记——可能它并不总是有用，但肯定不会有什么坏处。