已通过的 iPhone 未记录的 API
是否有人使用“未记录的 API”创建了 iPhone 应用程序并获得了批准？ 如果是这样，您能否向全世界分享您的流程以及对可能支持您观点的 Apple 审查的任何后续回应？
Has anyone created an iPhone app with "undocumented APIs" and made it through approval?
If so, could you share your processes to the world and any follow-up responses to Apple review that may have made your case?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
据我所知，允许访问实时相机图像的 API 不是公开的，但有许多应用程序使用它们。 其中一些甚至还被苹果公司推荐。
在这些案例中，使用未记录的 API 似乎并没有妨碍 Apple 的批准，但也有其他案例使用了相同的 API 集但未获得批准。 您可能想阅读 http://www.appleiphonereview.com/新闻/apple-blocks-video-camera-app/。
总而言之，对我来说，使用未记录的 API 似乎是一项非常危险的事情。 最终苹果掌握了所有的牌。 您是否想浪费时间开发一些可能会被拒绝的东西？
As far as I am aware, the APIs that allow access to live camera images are not public, yet there are many applications that use them. Some of these have even been featured by Apple.
It seems in these cases that use of undocumented APIs has not prevented Apple approval, but there have been other instances with the same set of APIs that have not been approved. You might want to read http://www.appleiphonereview.com/news/apple-blocks-video-camera-app/.
All in all, playing with undocumented APIs seems like a very risky business to me. Ultimately Apple hold all of the cards. Do you want to potentially waste your time developing something that will be rejected?
http://news.cnet.com/8301-13579_3-10108348-37。 html
Google 的搜索应用程序使用未记录的 API，但已通过审核流程。 据我了解，在这种情况下，普通开发人员不会获得批准 - 谷歌只是“特殊”。
http://news.cnet.com/8301-13579_3-10108348-37.html
Google's search app uses undocumented API's, but made it through the review process. From what I understand regular developers won't get approved under these circumstances- Google is just "Special".
我忘记了该应用程序的名称，但我读到有人花时间重新实现 Cover Flow，但当他最初将其提交给 Apple 审批时仍然被拒绝。
虽然这是几个月前的事，因此苹果可能会从那时起改变他们的流程，但这表明他们没有一个自动流程来检查未经授权的 API 的使用。 如果情况仍然如此，则意味着您对“未记录的 API”的使用可能会被忽视，除非它非常明显并且审阅者可以注视其使用。
话虽如此，你真的愿意冒这个险吗？ 您可能不喜欢这些规则，但在注册开发者计划时您确实同意了这些规则。 与某些“品味”拒绝不同，这条规则一点也不含糊。
I forget the name of the app, but I read about someone who took the time to reimplement Cover Flow and yet still got rejected when he originally submitted it to Apple for approval.
While this was a few months ago, and so Apple could have altered their process since then, this suggests that they don't have an automated process that checks for the use of unauthorised API. If that's still true, it means that your use of "undocumented APIs" would probably go unnoticed unless it was very obvious and a reviewer could eyeball their use.
Having said that, do you really want to take the risk? You may not like the rules but you did agree to them when you signed up to the developer programme. It's not as though this rule is at all ambiguous, unlike some of the "taste" rejections.