臨近年底手裡的app都要上線，不知道大家有沒有感覺這段時間的稽核團隊各種嚴，手裡的3個專案全部被卡（3個不同賬號），其中兩個是迭代，一個是新上線的app。全部都遭到了毒手~~~~(>_<)~~~~ 下面我就我遇見的問題做一下總結，希望可以幫到正在困惑中的你。
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.
這個問題很簡單就是說自己的截圖不能反應自己App的主要功能，然後重新換了截圖（我是主要截了下自己的App的幾個模組）就可以了
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.
這個問題寫的很清楚，說是在IPad上 IPv6網路下進行內購的時候支付不成功，老是支付失敗
當我收到這個郵件的時候我就立刻做了開始測試，模擬IPv6網路 然後用iPhone 和iPad 都進行了測試，發現內購是完全可以的，只是在IPad 上面內購回撥有點慢，然後我就截圖給他們告訴他們經過測試內購是可以完成的沒有問題的，然後晚上就等他們的回覆。他們的郵件回覆一般都是晚上1點之後（那個時候他們是早上8點多），等到晚上收到郵件還是說內購不行，還附帶了一樣的截圖。然後我就奇怪了，怎麼可能會這個樣子呢，明明沒有問題的他們怎麼老是支付不成功呢，突然我發現一個問題，難道他們測支付不是用的沙盒測試賬號？因為我的app 是新上的專案 內購專案還沒有稽核通過，如果不用沙盒測試賬號就一定會購買失敗，難道他們不是用的沙盒測試賬號?不會吧！ 雖然我不相信他們會這麼傻，但是我也沒有其他的辦法可以處理了。 ######之後我又回覆郵件給他們說我的內購專案還沒有過稽核，內購測試必須用沙盒賬號測試，然後又錄製了視訊傳到了YouTube 證明在IPad 上內購是可以完成的。 然後有經過一天的等待晚上的時候收到了蘋果的郵件回覆：
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
說感謝你的回覆，我們再繼續稽核您的App。（說真的當時收到這個郵件的時候我並沒有開心，我以為我們回覆的次數太多他們煩了？這是要掛起我的App了？要過就過不過就不過唄，什麼叫做繼續稽核,難道這就是傳說中的延期稽核嗎？），當時有點擔心的睡下了... 然而第二天我突然你發現竟然過了！開心的我在地鐵裡蹦了起來！
這個問題總結來說，如果自己真的沒有問題就大膽的去據理力爭吧，雖然稽核變得很嚴但是沒問題就是沒問題，可以錄視訊截圖證明自己的清白?
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.
這個問題是說我們在專案中使用到相機許可權，卻沒有告訴使用者什麼地方使用到這個許可權
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.
這個是說我的App用了內購之外的其他第三方支付（其實我們是做了隱形開關的），這個問題比較嚴重的，稽核團隊直接說你們的專案無法在加速，下次稽核時間會比較長，這種問題如果你也準備這麼做，建議最好現在不要，最近這個問題卡的非常嚴，處罰的也很重。 最好還是老老實實的刪除掉了第三方支付換成了內購！
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.
這個問題說是我們使用了定位功能卻沒有說明哪裡使用了定位卻沒有在許可權中說明。 但是我們的應用沒有使用定位，也沒有寓見這個字眼，然後就非常莫名其妙，然後我就回復郵件告訴他們我們沒有使用到定位功能，也從來沒有使用這個字眼。 然後他們回覆郵件說好吧，那你繼續改其他問題吧..... (還有其他的問題就是上面的內購)。 好吧，搞不懂怎麼擷取到這樣的圖，懷疑是其他應用彈出的！
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也能使用，處理方法是支援網頁的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.
我們注意到您的應用需要使用者註冊個人資訊才能購買非基於帳戶的應用內購買產品，這些產品不符合“App Store評論指南”。 這個問題我之前在另一個App 就遇見過一次，當時我記得我是發郵件申述了下，說明我們的App 必須要登入才能購買商品，因為我們的商品是必須依託賬號什麼的巴拉巴拉的..... 具體什麼我也忘了，當然如果你覺得可以說的清楚也可以試試，如果不行就要老實改下了，改成遊客也能購買商品，最好是做到根據iCoud 儲存下購買記錄，以便跨裝置使用。
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.
這個問題可能是最近爆出的一個終極大boss了，直接說的下次提交如果再出現其中的問題就直接刪除應用甚至封號。當時看到這個我嚇了一跳.這麼多問題..... 後來發現好多人都收到了這封郵件. 而且很多App都沒有違反上面的任何一條就也收到了這個. 足以證明收到這條郵件並不代表你有上述的所有問題，你要自己逐項審查下，如果沒有也是可以回覆郵件的（目前已知的有人回覆郵件說自己沒有出現 以上問題也通過稽核的了）當然這個也要根據你自己的專案情況做處理，但是有一點是可以肯定的就是如果你真的有問題有收到了這封郵件那你就要好好處理下了，因為你很可能已經被盯上和針對了,下一次提交一定會被重點對待的。