iOS>>分享工具>>警告:有没有办法摆脱警告/苹果审查会拒绝该项目吗
我正在我的应用程序中实现ShareKit。一切工作正常,但有许多由 ShareKit 文件引起的警告。
当我研究它们时,似乎它们都与几个问题有关:
- ShareKit 正在使用一些已弃用的项目(主要是“字体”相关)。
- FBLOG2 - ShareKit多次调用此功能,但不使用它;因此警告始终为: 表达式结果未使用
- 在 FBRequest.m 文件中,有一个名为“(id)parseXMLResponse:(NSData*)data error:(NSError**)error”的方法。我收到的警告是“语义问题:从不兼容的类型'FBXMLHandler *'分配给'id'”
任何人都可以指导我如何解决这些警告吗?
或者...有谁知道 Apple App Review 是否会拒绝携带这些警告的应用程序(正如我所说,除了调用警告这一事实之外,我的应用程序运行良好,并且我实现的所有 ShareKit 功能也运行良好) )?
I'm implementing ShareKit in my app. Everything is working fine, but there are many warnings caused by the ShareKit files.
When I look into them it seems that they all relate to just a few issues:
- ShareKit is using some deprecated items (mostly "font" related).
- FBLOG2 - many times ShareKit calling this feature, but don't use it; so the warning is always: Expresion result unused
- In FBRequest.m file there is a method called "(id)parseXMLResponse:(NSData*)data error:(NSError**)error". the warning I get is "Semantic Issue: Assigning to 'id' from incompatible type 'FBXMLHandler *'"
Can anyone direct me to how to solve these warnings?
OR... Does anyone know if Apple App Review rejects applications that carry these warnings (as I said, besides the fact that the warnings are being called, my app is working fine and all the ShareKit features I had implemented are functioning fine as well)?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
Sharekit 作者已经一年多没有更新了。话虽如此,从那时起,有些事情已经发生了变化(API 更新、方法已弃用等),但是 Sharekit 应该仍然可以工作。如果这些警告让您感到困扰(它们应该如此),那么修复它们应该不会很难。如果您需要帮助,请搜索具体警告。
例如,字体问题只是
setFont
已被弃用,取而代之的是cell.textLabel.font = ...
Sharekit hasn't been updated by the authors in over a year. That being said, some things have changed since then (APIs updated, method deprecated, etc.) However, Sharekit should still work. If the warnings bother you (as they should), they shouldn't be very difficult to fix. If you need help, google the specific warnings.
For example, the font issue is just
setFont
has been deprecated in favor ofcell.textLabel.font = ...