针对 beta iOS 版本测试 iOS 应用程序的推荐方法
能够针对 iOS 的 Beta 版本测试应用程序是件好事，但 Apple 推出的 Beta 版本的数量似乎在几个方面将仁慈变成了烦恼：
- SDK 的大量文件下载和 iOS 图像
- 必须保留修复一些东西，这些东西可能会在下一个测试版中被破坏
- Apple 的发行说明通常不足以让我弄清楚为什么我的应用程序违反了
- NDA 使得在网络上找到答案变得更加困难
所以，我开始想知道，如何其他 iOS 开发人员也处理这个问题。 Apple 是否有推荐的方法来测试频繁发布的测试版应用程序？我应该什么时候向 Apple 提交新 iOS 的修复程序（请记住，它可能会在下一个测试版本中被破坏）？
有人可以建议或指出一种针对 iOS 测试版测试应用程序的可行方法吗？
It is good to be able to test apps against beta releases of iOS, but the number of beta releases Apple is pushing out seems to turn the benevolence into annoyance for me on several bases:
- huge file downloads for the SDK and iOS images
- having to keep fixing things, which may be broken in the next beta
- the release notes from Apple is often not enough for me to figure out why my apps break
- the NDA makes it much more difficult to find an answer on the Web
So, I started wondering, how other iOS developers deal with this. Does Apple have a recommended approach to test apps with their frequent beta releases? When should I submit the fixes to Apple for the new iOS (keeping in mind that it might be broken in the next beta relesae)?
Could someone please suggest or point me to a plausible approach to test apps against beta iOS releases?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
一旦 GM 版本的操作系统和 SDK 发布，您至少还有一周的时间才能公开。这应该足以修复任何与 iOS 版本相关的错误、提交更新并使其被接受。如果您担心在操作系统公开发布之前它还没有准备好，您可以请求加急审核，并说明应用程序在新操作系统上崩溃的原因。
至于 beta 操作系统版本可能出现的问题，讨论起来太笼统，我们无法在这里讨论特定的 iOS 5 问题。
Once a GM version of the OS and SDK is out, you have at least a week before it goes public. This should be enough to fix any iOS version-related bugs, submit the update and get it accepted. If you are afraid it will not be ready before public release of the OS, you can request an expedited review and state that app breaks on new OS as a reason.
As for things that can go wrong with beta OS versions, it's too general to discuss, and we can't discuss particular iOS 5 problems here.