寫(xiě)的應(yīng)用即將要上架了,一看包名還是com.myproject,因?yàn)楫?dāng)時(shí)init的時(shí)候項(xiàng)目名是myproject,這個(gè)就肯定不行了,于是按照公司要求要改成域名反向的包名,比如我...
寫(xiě)的應(yīng)用即將要上架了,一看包名還是com.myproject,因?yàn)楫?dāng)時(shí)init的時(shí)候項(xiàng)目名是myproject,這個(gè)就肯定不行了,于是按照公司要求要改成域名反向的包名,比如我...
2018年3月14日 上午2:59發(fā)件人 Apple1.1 Legal: Privacy - Data Collection and StorageGuideline 5.1...
@winnie小雨 哈哈能幫到你我很開(kāi)心
weex 項(xiàng)目打包審核ios被拒!使用私有APIGuideline 2.3.1 - Performance We continue to find that your app contains hidden feature...
使用RN編寫(xiě)完簡(jiǎn)單的第一版應(yīng)用后,才發(fā)現(xiàn)還沒(méi)有添加啟動(dòng)圖,各種查找如何添加,不過(guò)資料不多再加上好多已經(jīng)過(guò)時(shí)過(guò)程還是比較痛苦的,所以把這個(gè)過(guò)程記錄下來(lái)。 使用react-nat...
在RN新的版本中,去除了index.android.js與index.ios.js移動(dòng)端入口文件,改成了只有一個(gè)index.js兩端通用的入口文件,在第一次運(yùn)行android...
由于最近要用RN寫(xiě)app,就趕緊看看,可是沒(méi)有那么多時(shí)間,就一邊看一邊寫(xiě)了,所以學(xué)的沒(méi)有那么細(xì)很多坑, 先來(lái)實(shí)現(xiàn),最后來(lái)看看坑吧 運(yùn)行環(huán)境:RN版本0.48以上使用最新官網(wǎng)推...
Guideline 2.3.1 - Performance We continue to find that your app contains hidden feature...
前言:最近要求要寫(xiě)單元測(cè)試了,可是對(duì)單元測(cè)試并沒(méi)有什么了解,于是趕緊各種google。最后簡(jiǎn)單的來(lái)說(shuō),就是與真實(shí)業(yè)務(wù)邏輯代碼完全隔離的另一份差不多相同的代碼,這些代碼就叫測(cè)試...
@一縷殤流化隱半邊冰霜 謝謝你你說(shuō)的很對(duì)
Weex 是如何在 iOS 客戶(hù)端上跑起來(lái)的前言 2016年4月21日,阿里巴巴在Qcon大會(huì)上宣布跨平臺(tái)移動(dòng)開(kāi)發(fā)工具Weex開(kāi)放內(nèi)測(cè)邀請(qǐng)。Weex能夠完美兼顧性能與動(dòng)態(tài)性,讓移動(dòng)開(kāi)發(fā)者通過(guò)簡(jiǎn)捷的前端語(yǔ)法寫(xiě)出Nativ...
前言 2016年4月21日,阿里巴巴在Qcon大會(huì)上宣布跨平臺(tái)移動(dòng)開(kāi)發(fā)工具Weex開(kāi)放內(nèi)測(cè)邀請(qǐng)。Weex能夠完美兼顧性能與動(dòng)態(tài)性,讓移動(dòng)開(kāi)發(fā)者通過(guò)簡(jiǎn)捷的前端語(yǔ)法寫(xiě)出Nativ...
應(yīng)用程序商店不允許使用非公共API,因?yàn)槿绻@些API改變,就會(huì)導(dǎo)致用戶(hù)體驗(yàn)不佳。
使用grep -r xxxx命令對(duì)蘋(píng)果說(shuō)的那些API檢查后發(fā)現(xiàn)有以下地方引用了這些API:
Binary file ./Pods/ATSDK-Weex/ATSDK.framework/ATSDK matches
Binary file ./Pods/ATSDK-Weex/ATSDK.framework/Versions/A/ATSDK matches
Binary file ./Pods/ATSDK-Weex/ATSDK.framework/Versions/Current/ATSDK matches
Binary file ./WeexDemo.xcworkspace/xcuserdata/mac.xcuserdatad/UserInterfaceState.xcuserstate matches
Weex 是如何在 iOS 客戶(hù)端上跑起來(lái)的前言 2016年4月21日,阿里巴巴在Qcon大會(huì)上宣布跨平臺(tái)移動(dòng)開(kāi)發(fā)工具Weex開(kāi)放內(nèi)測(cè)邀請(qǐng)。Weex能夠完美兼顧性能與動(dòng)態(tài)性,讓移動(dòng)開(kāi)發(fā)者通過(guò)簡(jiǎn)捷的前端語(yǔ)法寫(xiě)出Nativ...
作者你好,現(xiàn)在我們公司就是用的weex構(gòu)建的審核,蘋(píng)果提示說(shuō)第三方框架有引用的私有API他們不予許,具體拒絕通過(guò)信息如下:懇請(qǐng)幫助,,,,
Guideline 2.3.1 - Performance
We discovered that your app contains hidden features.
The next submission of this app may require a longer review time.
Next Steps
- Review the Performance section of the App Store Review Guidelines.
- Ensure your app is compliant with all sections of the App Store Review Guidelines and the Terms & Conditions of the Apple Developer Program.
- Once your app is fully compliant, resubmit your app for review.
Your app uses or references the following non-public APIs:
kIOMasterPortDefault, _IOServiceMatching, _IOServiceGetMatchingService, _IORegistryEntryCreateCFProperties, _IOObjectRelease
The use of non-public APIs is not permitted on the App Store because it can lead to a poor user experience should these APIs change.
Next Steps
If you are using third-party libraries, please update to the most recent version of those libraries. If you do not have access to the libraries' source, you may be able to search the compiled binary using the "strings" or "otool" command line tools. The "strings" tool can output a list of the methods that the library calls and "otool -ov" will output the Objective-C class structures and their defined methods. These tools can help you narrow down where the problematic code resides. You could also use the "nm" tool to verify if any third-party libraries are calling these APIs.
Resources
For information on the "nm" tool, please review the "nm tool" Xcode manual page.
Weex 是如何在 iOS 客戶(hù)端上跑起來(lái)的前言 2016年4月21日,阿里巴巴在Qcon大會(huì)上宣布跨平臺(tái)移動(dòng)開(kāi)發(fā)工具Weex開(kāi)放內(nèi)測(cè)邀請(qǐng)。Weex能夠完美兼顧性能與動(dòng)態(tài)性,讓移動(dòng)開(kāi)發(fā)者通過(guò)簡(jiǎn)捷的前端語(yǔ)法寫(xiě)出Nativ...