问了一下个推的技术支持,说是要更新sdk,这个啥时候更新啊?
- 发布:2017-03-13 09:54
- 更新:2017-03-16 11:07
- 阅读:2331
最佳回复
BoredApe - 有问题就会有答案。
关于Appstore 违反政策的警告,云端打包机(Alpha)已更换最新高德和个推SDK (如果有Alpha版本HBuilder 请直接打包即可 如没有 请下载对应版本进行打包)
公网地址:
Win版本:http://update.dcloud.net.cn/alpha/HBuilder.windows@20170316.zip
Mac版本:http://update.dcloud.net.cn/alpha/HBuilder.macosx_64@20170316.tar.gz
注意,HBuilder for Mac alpha 是没有签名的,如Mac系统设置了仅信任AppStore或受信任的开发者来源的安装包,请右键点击打开或control+点击打开HBuilder
zhongjie_yang (作者)
好的,谢谢
2017-03-15 13:58
zhongjie_yang (作者)
更新了木有???咋没个通知啥的。你们就不能建个开发者群么
2017-03-16 10:05
BoredApe
打包机还在调整,没有更新.. 官方群 在这个帖子右上角你的头像下面
2017-03-16 10:38
BoredApe
打包机已更新 ,请重新打包提交即可
2017-03-16 11:07
rumeng
回复 BoredApe:ios离线打包的sdk有更新吗?
2017-03-27 12:26
BoredApe
请参考:http://ask.dcloud.net.cn/article/1237
2017-03-27 13:28
rumeng
回复 BoredApe:昨天已经重新在线打包,提交上传,还是没有通过,错误是相同的: 2. 5 Performance: Software Requirements (iOS)
Guideline 2.5.2 - Performance
Your app, extension, or linked framework appears to contain code designed explicitly with the capability to change your app’s behavior or functionality after App Review approval, which is not in compliance with App Store Review Guideline 2.5.2 and section 3.3.2 of the Apple Developer Program License Agreement.
This code, combined with a remote resource, can facilitate significant changes to your app’s behavior compared to when it was initially reviewed for the App Store. While you may not be using this functionality currently, it has the potential to load private frameworks, private methods, and enable future feature changes. This includes any code which passes arbitrary parameters to dynamic methods such as dlopen(), dlsym(), respondsToSelector:, performSelector:, method_exchangeImplementations(), and running remote scripts in order to change app behavior and/or call SPI, based on the contents of the downloaded script. Even if the remote resource is not intentionally malicious, it could easily be hijacked via a Man In The Middle (MiTM) attack, which can pose a serious security vulnerability to users of your app.
Next Steps
To resolve this issue, please perform an in-depth review of your app and remove any code, frameworks, or SDKs that fall in line with the functionality described above and resubmit your app’s binary for review.
2017-03-28 08:46