1.Guideline 2.2 - Performance - Beta Testing
Your app appears to be a pre-release, test, or trial version with a limited feature set. Apps that are created for demonstration or trial purposes are not appropriate for the App Store.Please see attached screenshots for details.Next StepsTo resolve this issue, please complete, remove, or fully configure any partially implemented features. Additionally, remove all references to "demo," "trial," "beta," or "test" in your app description, app icon, screenshots, previews, release notes, and binary.
解決辦法:刪除所有的“demo”幢踏，“試用”，“beta”链峭，或者“測試”在你的應(yīng)用程序描述，應(yīng)用程序圖標电禀，屏幕截圖扣甲，預(yù)覽鸽凶，發(fā)布說明币砂，和二進制。
2.Guideline 5.0 - LegalYour app contains content - or facilitates, enables, and encourages an activity - that is not legal in all of the locations where the app is available. Please see attached screenshots for details.Next StepsTo resolve this issue, please remove all content and features that are illegal in the locations where your app is available. Please note that app concepts that are considered illegal are not allowed on the App Store.
解決辦法:這個問題已經(jīng)觸碰到了蘋果的底線,刪除在您的應(yīng)用程序可用的位置上非法的所有內(nèi)容和特性玻侥。請注意决摧，在app Store中不允許使用被認為是非法的app概念。
3.Guideline 4.2.3 - Design - Minimum FunctionalityWe were required to install the WeChat and QQ apps before we could log in via WeChat and QQ. Users should be able to log in with WeChat and QQ and access their accounts without having to install any additional apps.Next StepsIf you would like to offer authentication through WeChat and QQ, please use a mechanism that allows users to log in with WeChat and 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.ResourcesFor additional information on the Safari View Controller API, please review the What's New in Safari webpage.
解決辦法:傳統(tǒng)的依靠第三方是否安裝來判斷是否顯示微信QQ的登錄圖標已經(jīng)無法滿足所有的蘋果測試人員的要求.需要依靠后臺的參數(shù)來判斷是否顯示第三方登錄圖標.
4.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.
解決辦法:這個問題很簡單就是說自己的截圖不能反應(yīng)自己App的主要功能凑兰，然后重新?lián)Q了截圖（我是主要截了下自己的App的幾個模塊）就可以了
5.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.
解決辦法:內(nèi)購項目還沒有過審核掌桩，內(nèi)購測試必須用沙盒賬號測試，然后又錄制了視頻傳到了YouTube 證明在IPad 上內(nèi)購是可以完成的姑食。(錄制視頻有時候能夠給項目的審核起到很大的作用)
6.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.
解決辦法:這個經(jīng)常遇見,蘋果的所有權(quán)限獲取都要說明打開權(quán)限的目的是干什么.
7.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用了內(nèi)購之外的其他第三方支付（其實我們是做了隱形開關(guān)的）拘鞋，這個解決辦法:App用了內(nèi)購之外的其他第三方支付（其實是做了隱形開關(guān)的），這個問題比較嚴重的矢门，審核團隊直接說你們的項目無法在加速盆色，下次審核時間會比較長，這種問題如果你也準備這么做祟剔，建議最好現(xiàn)在不要隔躲，最近這個問題卡的非常嚴，處罰的也很重物延。 最好還是老老實實的刪除掉了第三方支付換成了內(nèi)購
8.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.
解決辦法:增加游客模式.辦法有二:1測試顯示游客模式,上架隱藏游客模式2.制作一套游客模式下的操作流程,增加游客功能.
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了,后來發(fā)現(xiàn)好多人都收到了這封郵件. 而且很多App都沒有違反上面的任何一條就也收到了這個. 足以證明收到這條郵件并不代表你有上述的所有問題.但是有一點是可以肯定的就是如果你真的有問題有收到了這封郵件那你就要好好處理下了宣旱，因為你很可能已經(jīng)被盯上和針對了,下一次提交一定會被重點對待的。
We?discovered?one?or?more?bugs?in?your?app?when?reviewed?on?iPad?and?iPhone?running?iOS?10.2?on?Wi-Fi?connected?to?an?IPv6?network.
Specifically,?we?were?still?unable?access?your
app…
解決辦法:如果App本身不兼容ipv6叛薯，最好的辦法是讓App本身兼容ipv6或通過升級服務(wù)器來支持ipv6浑吟；如果App本身已兼容ipv6，是審核人員所在的網(wǎng)絡(luò)環(huán)境導致的問題耗溜，其解決方式主要有截圖或拍下視頻向蘋果申訴组力，或嘗試多次提交審核
The?Seller?and?Artist?names?associated?with?your?app?do?not?reflect?the?financial?institute?in?the?app?or?its?metadata,?as?required?by?section?1.2?of?theApple?Developer?Program?License?Agreement.
Next Steps
Your?app?must?be?published?under?a?Seller?name?and?Artist?name?that?reflects?the?financial?institution?brand…
理財、P2P等金融類相關(guān)產(chǎn)品的開發(fā)者：如果開發(fā)商的名稱和App內(nèi)的金融機構(gòu)名字不匹配抖拴，被拒的風險就會大大增加
