iOS 最新審核被拒及解決方案 (包括2.1大禮包)

臨近年底手里的app都要上線叽掘,不知道大家有沒有感覺這段時(shí)間的審核團(tuán)隊(duì)各種嚴(yán)章办,手里的3個(gè)項(xiàng)目全部被卡(3個(gè)不同賬號),其中兩個(gè)是迭代吩谦,一個(gè)是新上線的app。全部都遭到了毒手~~~(>_<)~~~
下面我就我遇見的問題做一下總結(jié)膝藕,希望可以幫到正在困惑中的你式廷。

Guideline 2.3.3 - Performance - Accurate Metadata

We noticed that your screenshots do not sufficiently reflect your app in use.
Please see attached screenshots for details.
Next Steps
To resolve this issue, please revise your screenshots to ensure that they accurately reflect the app in use on the supported devices. For iPhone, you need a set of 5.5-inch display screenshots and for iPad, you need a set for 12.9-inch display. This set will be scaled appropriately down to other device sizes when viewed on the App Store in each territory.
Resources
For resources on creating great screenshots for the App Store, you may want to review the App Store Product Page information available on the Apple developer portal.
Please ensure you have made any screenshot modifications using Media Manager. You should confirm your app looks and behaves identically in all languages and on all supported devices. Learn how to use Media Manager to add custom screenshots for each display size and localization.
Since your iTunes Connect status is Metadata Rejected, we do NOT require a new binary. To revise the metadata, visit iTunes Connect to select your app and revise the desired metadata values. Once you’ve completed all changes, reply to this message in Resolution Center and we will continue the review.
NOTE: Please be sure to make any metadata changes to all app localizations by selecting each specific localization and making appropriate changes.

這個(gè)問題很簡單就是說自己的截圖不能反應(yīng)自己App的主要功能,然后重新?lián)Q了截圖(我是主要截了下自己的App的幾個(gè)模塊)就可以了

Guideline 2.1 - Performance - App Completeness

We discovered one or more bugs in your app when reviewed on iPad running iOS 11.2.5 on Wi-Fi connected to an IPv6 network.
Specifically, the In-App Purchase (IAP) results in an error.
Below are the steps to reproduce the issue:
1. Launch the application
2. Navigate to Purchase/Recharge tab
3. Proceed to purchase one of the IAP products
4. IAP confirmation window appears
5. Confirm Purchase
6. IAP results in an error
The review was conducted under sandbox environment.
Please see attached screenshots for details.
Next Steps
To resolve this issue, please run your app on a device to identify any issues, then revise and resubmit your app for review.
If we misunderstood the intended behavior of your app, please reply to this message in Resolution Center to provide information on how these features were intended to work.
For new apps, uninstall all previous versions of your app from a device, then install and follow the steps to reproduce the issue. For updates, install the new version as an update to the previous version, then follow the steps to reproduce the issue.
Resources
For information about testing your app and preparing it for review, please see Technical Note TN2431: App Testing Guide.
For a networking overview, please review About Networking. For a more specific overview of App Review’s IPv6 requirements, please review the IPv6 and App Review discussion on the Apple Developer Forum.

1.png

這個(gè)問題寫的很清楚芭挽,說是在IPad上 IPv6網(wǎng)絡(luò)下進(jìn)行內(nèi)購的時(shí)候支付不成功滑废,老是支付失敗

當(dāng)我收到這個(gè)郵件的時(shí)候我就立刻做了開始測試,模擬IPv6網(wǎng)絡(luò) 然后用iPhone 和iPad 都進(jìn)行了測試袜爪,發(fā)現(xiàn)內(nèi)購是完全可以的蠕趁,只是在IPad 上面內(nèi)購回調(diào)有點(diǎn)慢,然后我就截圖給他們告訴他們經(jīng)過測試內(nèi)購是可以完成的沒有問題的辛馆,然后晚上就等他們的回復(fù)俺陋。他們的郵件回復(fù)一般都是晚上1點(diǎn)之后(那個(gè)時(shí)候他們是早上8點(diǎn)多),等到晚上收到郵件還是說內(nèi)購不行昙篙,還附帶了一樣的截圖腊状。然后我就奇怪了,怎么可能會這個(gè)樣子呢苔可,明明沒有問題的他們怎么老是支付不成功呢缴挖,突然我發(fā)現(xiàn)一個(gè)問題,難道他們測支付不是用的沙盒測試賬號焚辅?因?yàn)槲业腶pp 是新上的項(xiàng)目 內(nèi)購項(xiàng)目還沒有審核通過映屋,如果不用沙盒測試賬號就一定會購買失敗,難道他們不是用的沙盒測試賬號?不會吧同蜻! 雖然我不相信他們會這么傻秧荆,但是我也沒有其他的辦法可以處理了。

之后我又回復(fù)郵件給他們說我的內(nèi)購項(xiàng)目還沒有過審核埃仪,內(nèi)購測試必須用沙盒賬號測試乙濒,然后又錄制了視頻傳到了YouTube 證明在IPad 上內(nèi)購是可以完成的。

然后有經(jīng)過一天的等待晚上的時(shí)候收到了蘋果的郵件回復(fù):

Hello,
Thank you for your response.
We will continue to review your app, and will notify you if there are any further issues.
Best regards,
App Store Review

說感謝你的回復(fù),我們再繼續(xù)審核您的App颁股。(說真的當(dāng)時(shí)收到這個(gè)郵件的時(shí)候我并沒有開心么库,我以為我們回復(fù)的次數(shù)太多他們煩了?這是要掛起我的App了甘有?要過就過不過就不過唄诉儒,什么叫做繼續(xù)審核,難道這就是傳說中的延期審核嗎?)亏掀,當(dāng)時(shí)有點(diǎn)擔(dān)心的睡下了... 然而第二天我突然你發(fā)現(xiàn)竟然過了忱反!開心的我在地鐵里蹦了起來!

這個(gè)問題總結(jié)來說滤愕,如果自己真的沒有問題就大膽的去據(jù)理力爭吧温算,雖然審核變得很嚴(yán)但是沒問題就是沒問題,可以錄視頻截圖證明自己的清白??

Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage

We noticed that your app requests the user’s consent to access their Camera but does not clarify the use of this feature in the permission modal alert.
Next Steps
To resolve this issue, please revise the permission modal alert to specify why the app is requesting access to the user's Camera.
Resources
To learn more about requesting the user’s permission to access app features, visit the iOS Human Interface Guidelines. You may also want to review the Technical Q&A QA1937: Resolving the Privacy-Sensitive Data App Rejection page for details on how to provide a usage description for permission request alerts.

這個(gè)問題是說我們在項(xiàng)目中使用到相機(jī)權(quán)限间影,卻沒有告訴用戶什么地方使用到這個(gè)權(quán)限


這里改成在什么服務(wù)中使用到相機(jī)就可以了注竿,給過了!

Guideline 3.1.1 - Business - Payments - In-App Purchase

We noticed that your app or its metadata enables the purchase of content, services, or functionality in the app by means other than the in-app purchase API, which is not appropriate for the App Store.
The next submission of this app may require a longer review time, and this app will not be eligible for an expedited review until this issue is resolved.
Next Steps

  • Review the In-App Purchase 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.
    If you believe your app is compliant with the App Store Review Guidelines, you may submit an appeal. Alternatively, you may provide additional details about your app by replying directly to this message.
    In-App Purchase
    It may be appropriate to revise your app to use the in-app purchase API to provide content purchasing functionality.
    In-app purchase provides several benefits, including:
  • The flexibility to support a variety of business models.
  • Impacting your app ranking by consolidating your sales to one app rather than distributing them across multiple apps.
  • An effective marketing vehicle to drive additional sales of new content.
    For information on in-app purchase, please refer to the following documentation:
    In-App Purchase for Developers
    In-App Purchase Programming Guide
    For step-by-step instructions on in-app purchase creation within iTunes Connect, refer to In-App Purchase for Developers.

這個(gè)是說我的App用了內(nèi)購之外的其他第三方支付(其實(shí)我們是做了隱形開關(guān)的)魂贬,這個(gè)問題比較嚴(yán)重的巩割,審核團(tuán)隊(duì)直接說你們的項(xiàng)目無法在加速,下次審核時(shí)間會比較長付燥,這種問題如果你也準(zhǔn)備這么做宣谈,建議最好現(xiàn)在不要,最近這個(gè)問題卡的非常嚴(yán)键科,處罰的也很重闻丑。 最好還是老老實(shí)實(shí)的刪除掉了第三方支付換成了內(nèi)購!

Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage

We noticed that your app requests the user’s consent to access the Location services but does not clarify the use of this feature in the permission modal alert.
Please see attached screenshots for details.
Next Steps
To resolve this issue, please revise the permission modal alert to specify why the app is requesting access to the Location services.
Resources
To learn more about requesting the user’s permission to access app features, visit the iOS Human Interface Guidelines. You may also want to review the Technical Q&A QA1937: Resolving the Privacy-Sensitive Data App Rejection page for details on how to provide a usage description for permission request alerts.

2.png

這個(gè)問題說是我們使用了定位功能卻沒有說明哪里使用了定位卻沒有在權(quán)限中說明萝嘁。 但是我們的應(yīng)用沒有使用定位梆掸,也沒有寓見這個(gè)字眼扬卷,然后就非常莫名其妙牙言,然后我就回復(fù)郵件告訴他們我們沒有使用到定位功能,也從來沒有使用這個(gè)字眼怪得。 然后他們回復(fù)郵件說好吧咱枉,那你繼續(xù)改其他問題吧..... (還有其他的問題就是上面的內(nèi)購)。 好吧徒恋,搞不懂怎么截取到這樣的圖蚕断,懷疑是其他應(yīng)用彈出的!

Guideline 4.2.3 - Design - Minimum Functionality

We were required to install the QQ app before we could log in via QQ. Users should be able to log in with QQ and access their accounts without having to install any additional apps.
Next Steps
If you would like to offer authentication through QQ, please use a mechanism that allows users to log in with QQ from within your app without first having to install an additional app.
We recommend implementing the Safari View Controller API to display web content within your app. The Safari View Controller allows the display of a URL and inspection of the certificate from an embedded browser in an app so that customers can verify the webpage URL and SSL certificate to confirm they are entering their sign in credentials into a legitimate page.
Resources
For additional information on the Safari View Controller API, please review the What's New in Safari webpage.

qq第三方登錄必須安裝qq才行入挣,希望不安裝qq也能使用亿乳,處理方法是支持網(wǎng)頁的qq登錄

Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage

We noticed that your app requires users to register with personal information to purchase non account-based in-app purchase products, which does not comply with the App Store Review Guidelines.
Please see attached screenshot for details.
Apps cannot require user registration prior to allowing access to app content and features that are not associated specifically to the user.
Next Steps
User registration that requires the sharing of personal information must be optional or tied to account-specific functionality.
To resolve this issue, please make it clear to the user that registering will enable them to access the content from any of their iOS devices, and to provide them a way to register at any time, if they wish to later extend access to additional iOS devices.

我們注意到您的應(yīng)用需要用戶注冊個(gè)人信息才能購買非基于帳戶的應(yīng)用內(nèi)購買產(chǎn)品,這些產(chǎn)品不符合“App Store評論指南”。 這個(gè)問題我之前在另一個(gè)App 就遇見過一次葛假,當(dāng)時(shí)我記得我是發(fā)郵件申述了下障陶,說明我們的App 必須要登錄才能購買商品,因?yàn)槲覀兊纳唐肥潜仨氁劳匈~號什么的巴拉巴拉的..... 具體什么我也忘了聊训,當(dāng)然如果你覺得可以說的清楚也可以試試抱究,如果不行就要老實(shí)改下了,改成游客也能購買商品带斑,最好是做到根據(jù)iCoud 存儲下購買記錄鼓寺,以便跨設(shè)備使用。

Guideline 2.1 - Information Needed

This type of app has been identified as one that may violate one or more of the following App Store Review Guidelines. Specifically, these types of apps often:
1.1.6 - Include false information, features, or misleading metadata.
2.3.0 - Undergo significant concept changes after approval
2.3.1 - Have hidden or undocumented features, including hidden "switches" that redirect to a gambling or lottery website
3.1.1 - Use payment mechanisms other than in-app purchase to unlock features or functionality in the app
4.3.0 - Are a duplicate of another app or are conspicuously similar to another app
5.2.1 - Were not submitted by the legal entity that owns and is responsible for offering any services provided by the app
5.3.4 - Do not have the necessary licensing and permissions for all the locations where the app is used
Before we can continue with our review, please confirm that this app does not violate any of the above guidelines. You may reply to this message in Resolution Center or the App Review Information section in iTunes Connect to verify this app’s compliance.
Given the tendency for apps of this type to violate the aforementioned guidelines, this review will take additional time. If at any time we discover that this app is in violation of these guidelines, the app will be rejected and removed from the App Store, and it may result in the termination of your Apple Developer Program account.

這個(gè)問題可能是最近爆出的一個(gè)終極大boss了勋磕,直接說的下次提交如果再出現(xiàn)其中的問題就直接刪除應(yīng)用甚至封號妈候。當(dāng)時(shí)看到這個(gè)我嚇了一跳.這么多問題..... 后來發(fā)現(xiàn)好多人都收到了這封郵件. 而且很多App都沒有違反上面的任何一條就也收到了這個(gè). 足以證明收到這條郵件并不代表你有上述的所有問題,你要自己逐項(xiàng)審查下朋凉,如果沒有也是可以回復(fù)郵件的(目前已知的有人回復(fù)郵件說自己沒有出現(xiàn) 以上問題也通過審核的了)當(dāng)然這個(gè)也要根據(jù)你自己的項(xiàng)目情況做處理州丹,但是有一點(diǎn)是可以肯定的就是如果你真的有問題有收到了這封郵件那你就要好好處理下了,因?yàn)槟愫芸赡芤呀?jīng)被盯上和針對了,下一次提交一定會被重點(diǎn)對待的杂彭。

最后編輯于
?著作權(quán)歸作者所有,轉(zhuǎn)載或內(nèi)容合作請聯(lián)系作者
  • 序言:七十年代末墓毒,一起剝皮案震驚了整個(gè)濱河市,隨后出現(xiàn)的幾起案子亲怠,更是在濱河造成了極大的恐慌所计,老刑警劉巖,帶你破解...
    沈念sama閱讀 216,402評論 6 499
  • 序言:濱河連續(xù)發(fā)生了三起死亡事件团秽,死亡現(xiàn)場離奇詭異主胧,居然都是意外死亡,警方通過查閱死者的電腦和手機(jī)习勤,發(fā)現(xiàn)死者居然都...
    沈念sama閱讀 92,377評論 3 392
  • 文/潘曉璐 我一進(jìn)店門踪栋,熙熙樓的掌柜王于貴愁眉苦臉地迎上來,“玉大人图毕,你說我怎么就攤上這事夷都。” “怎么了予颤?”我有些...
    開封第一講書人閱讀 162,483評論 0 353
  • 文/不壞的土叔 我叫張陵囤官,是天一觀的道長。 經(jīng)常有香客問我蛤虐,道長党饮,這世上最難降的妖魔是什么? 我笑而不...
    開封第一講書人閱讀 58,165評論 1 292
  • 正文 為了忘掉前任驳庭,我火速辦了婚禮刑顺,結(jié)果婚禮上,老公的妹妹穿的比我還像新娘。我一直安慰自己蹲堂,他們只是感情好荞驴,可當(dāng)我...
    茶點(diǎn)故事閱讀 67,176評論 6 388
  • 文/花漫 我一把揭開白布。 她就那樣靜靜地躺著贯城,像睡著了一般熊楼。 火紅的嫁衣襯著肌膚如雪。 梳的紋絲不亂的頭發(fā)上能犯,一...
    開封第一講書人閱讀 51,146評論 1 297
  • 那天鲫骗,我揣著相機(jī)與錄音,去河邊找鬼踩晶。 笑死执泰,一個(gè)胖子當(dāng)著我的面吹牛,可吹牛的內(nèi)容都是我干的渡蜻。 我是一名探鬼主播术吝,決...
    沈念sama閱讀 40,032評論 3 417
  • 文/蒼蘭香墨 我猛地睜開眼,長吁一口氣:“原來是場噩夢啊……” “哼茸苇!你這毒婦竟也來了排苍?” 一聲冷哼從身側(cè)響起,我...
    開封第一講書人閱讀 38,896評論 0 274
  • 序言:老撾萬榮一對情侶失蹤学密,失蹤者是張志新(化名)和其女友劉穎淘衙,沒想到半個(gè)月后,有當(dāng)?shù)厝嗽跇淞掷锇l(fā)現(xiàn)了一具尸體腻暮,經(jīng)...
    沈念sama閱讀 45,311評論 1 310
  • 正文 獨(dú)居荒郊野嶺守林人離奇死亡彤守,尸身上長有42處帶血的膿包…… 初始之章·張勛 以下內(nèi)容為張勛視角 年9月15日...
    茶點(diǎn)故事閱讀 37,536評論 2 332
  • 正文 我和宋清朗相戀三年,在試婚紗的時(shí)候發(fā)現(xiàn)自己被綠了哭靖。 大學(xué)時(shí)的朋友給我發(fā)了我未婚夫和他白月光在一起吃飯的照片具垫。...
    茶點(diǎn)故事閱讀 39,696評論 1 348
  • 序言:一個(gè)原本活蹦亂跳的男人離奇死亡,死狀恐怖试幽,靈堂內(nèi)的尸體忽然破棺而出筝蚕,到底是詐尸還是另有隱情,我是刑警寧澤抡草,帶...
    沈念sama閱讀 35,413評論 5 343
  • 正文 年R本政府宣布饰及,位于F島的核電站蔗坯,受9級特大地震影響康震,放射性物質(zhì)發(fā)生泄漏。R本人自食惡果不足惜宾濒,卻給世界環(huán)境...
    茶點(diǎn)故事閱讀 41,008評論 3 325
  • 文/蒙蒙 一腿短、第九天 我趴在偏房一處隱蔽的房頂上張望。 院中可真熱鬧,春花似錦橘忱、人聲如沸赴魁。這莊子的主人今日做“春日...
    開封第一講書人閱讀 31,659評論 0 22
  • 文/蒼蘭香墨 我抬頭看了看天上的太陽颖御。三九已至,卻和暖如春凝颇,著一層夾襖步出監(jiān)牢的瞬間潘拱,已是汗流浹背。 一陣腳步聲響...
    開封第一講書人閱讀 32,815評論 1 269
  • 我被黑心中介騙來泰國打工拧略, 沒想到剛下飛機(jī)就差點(diǎn)兒被人妖公主榨干…… 1. 我叫王不留芦岂,地道東北人。 一個(gè)月前我還...
    沈念sama閱讀 47,698評論 2 368
  • 正文 我出身青樓垫蛆,卻偏偏與公主長得像禽最,于是被迫代替她去往敵國和親。 傳聞我的和親對象是個(gè)殘疾皇子袱饭,可洞房花燭夜當(dāng)晚...
    茶點(diǎn)故事閱讀 44,592評論 2 353