2019年開發(fā)的 top樂淘添坊，對(duì)于ｉＯＳ端TOP樂淘上線審核遇到的問題，總結(jié)了一下。

第二次提交反饋的是：

Guideline 2.1 - Performance - App Completeness

Your app crashed on iPhone running iOS 12.0.1 connected to an IPv6 network when we:

1. Launch app

2. Tap on 游客登錄

3. App crashes

We have attached detailed crash logs to help troubleshoot this issue.

Next Steps

To resolve this issue, please revise your app and test it on a device to ensure that it runs as expected.

Resources

For information on how to symbolicate and read a crash log, please review Tech Note TN2151 Understanding and Analyzing Application Crash Reports.

分析：連接iPv6卑吭，啟動(dòng)應(yīng)用程序點(diǎn)擊

客登錄應(yīng)用程序崩潰。原因是不支持ipv6马绝。

解決：第三方框架有的不支持ipv6豆赏，換成最新的（后面又給服務(wù)器添加支持ipv6）。

第三次提交：

Guideline 2.1 - Information Needed

We were unable to sign in to review your app with the demo account information you provided. In order for us to review your app, please provide us with a functional demo account so that we may fully assess your app's features.

Next Steps

To help us proceed with the review of your app, please provide a user name and password in the App Review Information section for your app in App Store Connect. Please be sure to include content in your app that demonstrates the features and functionality available in your app.

To provide demo account information:

• Log in to App Store Connect

• Click "My Apps"

• Select your app

• Click on the app version on the left side of the screen

• Scroll down to "App Review Information"

• Select the "Sign-in required" box

• Enter demo credentials in the "User name" and "Password" fields

• Once you've completed all changes, click the "Save" button at the top of the Version Information page.

Please see attached screenshots for details.

Since your App Store Connect status is Metadata Rejected, we do NOT require a new binary. To revise the metadata, visit App Store 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.

分析：因?yàn)槲业诙翁峤坏臅r(shí)候富稻，沒有去看之前的這個(gè)測試賬號(hào)掷邦，之前的那個(gè)賬號(hào)已經(jīng)修改了密碼，所以提示賬號(hào)密碼錯(cuò)誤椭赋；

解決：提供一個(gè)可以演示APP內(nèi)容的正確的賬號(hào)密碼耙饰。

第四次提交：

Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage

We noticed that your app requests the user’s consent to access their photos 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 photos.

The permission request alert should specify how your app will use this feature to help users understand why your app is requesting access to their personal data.

Resources

For additional information and instructions on configuring and presenting an alert, please review the Requesting Permission section of the iOS Human Interface Guidelines and the Information Property List Key Reference. 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.

Learn more about Protecting the User’s Privacy.

Please see attached screenshot for details.

分析：沒有添加是否允許APP訪問用戶照片和相機(jī)的權(quán)限；

解決：info.plist中添加權(quán)限

[圖片上傳失敗...(image-e8461b-1725608515419)]

第五次提交：

Guideline 2.1 - Information Needed

We were unable to sign in to review your app with the demo account information you provided. In order for us to review your app, please provide us with a functional demo account so that we may fully assess your app's features. Next Steps To help us proceed with the review of your app, please provide a user name and password in the App Review Information section for your app in App Store Connect. Please be sure to include content in your app that demonstrates the features and functionality available in your app. To provide demo account information: - Log in to App Store Connect - Click "My Apps" - Select your app - Click on the app version on the left side of the screen - Scroll down to "App Review Information" - Select the "Sign-in required" box - Enter demo credentials in the "User name" and "Password" fields - Once you've completed all changes, click the "Save" button at the top of the Version Information page. Please see attached screenshot for details.

第六次提交

Guideline 2.1 - Performance - App Completeness

Your app or its metadata does not appear to include final content.     Next Steps    To resolve this issue, please review your app and metadata to ensure that all of its content is final.    Please see attached screenshots for details.

分析：部分界面沒有數(shù)據(jù)纹份，顯示空白

解決：后臺(tái)添加數(shù)據(jù)，沒有數(shù)據(jù)的界面廷痘，app內(nèi)添加內(nèi)容為空提示蔓涧。

第七次提交，反饋回來兩個(gè)問題 Guideline 2.3.6 和 Guideline 4.3 - Design：

Guideline 2.3.6 - Performance - Accurate Metadata

The rating you have selected, 12+, is inconsistent with the content of your app. Since your app includes content and features involving alcohol, it should be rated appropriately for this subject. Next Steps To resolve this issue, please update your Rating selections in App Store Connect. - Log in to App Store Connect - Click on "My Apps" - Select your app - Click on the app version on the left side of the screen - Scroll down to select a Rating on the version information page - Click the Edit button next to "Rating" - Change the Rating selections - Click "Done" - Once you've completed all changes, click the "Save" button at the top of the App Version Information page. Note: Apps must be rated accordingly for the highest level of content that the user is able to access in the app.

分析：應(yīng)用程序包含酒精相關(guān)的內(nèi)容和功能笋额，因此應(yīng)該針對(duì)該主題進(jìn)行適當(dāng)?shù)脑u(píng)分 （酒類多次展示元暴，蘋果認(rèn)為 這些內(nèi)容可能會(huì)顯示可能令人反感的內(nèi)容，如裸露兄猩、色情和褻瀆內(nèi)容茉盏。）

解決：修改上傳時(shí)候的評(píng)分。

Guideline 4.3 - Design

We noticed that your app provides the same feature set as other apps submitted to the App Store; it simply varies in content or language, which is considered a form of spam.    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 Design section of the [<u>App Store Review Guidelines</u>](https://developer.apple.com/app-store/review/guidelines/).  - Ensure your app is compliant with all sections of the [<u>App Store Review Guidelines</u>](https://developer.apple.com/app-store/review/guidelines/) and the [<u>Terms & Conditions</u>](https://developer.apple.com/terms/) of the Apple Developer Program.   - Once your app is fully compliant, resubmit your app for review.    When creating multiple apps where content is the only varying element, you should offer a single app to deliver differing content to customers. If you would like to offer this content for purchase, it would be appropriate to use the in-app purchase API.    Alternatively, you may consider creating a web app, which looks and behaves similar to a native app when the customer adds it to their Home screen. Refer to the [<u>Configuring Web Applications</u>](https://developer.apple.com/library/content/documentation/AppleApplications/Reference/SafariWebContent/ConfiguringWebApplications/ConfiguringWebApplications.html) section of the Safari Web Content Guide for more information.    Submitting apps designed to mislead or harm customers or evade the review process may result in the termination of your Apple Developer Program account. Review the [<u>Terms & Conditions</u>](https://developer.apple.com/terms/) of the Apple Developer Program to learn more about our policies regarding termination.    If you believe your app is compliant with the [<u>App Store Review Guidelines</u>](https://developer.apple.com/app-store/review/guidelines/), you may submit an appeal. Alternatively, you may provide additional details about your app by replying directly to this message.    Please see attached screenshot for details.

分析：被蘋果認(rèn)定是馬甲包問題

解決：修改了項(xiàng)目的名稱和各個(gè)文件名稱和部分的類名枢冤，提交還是被拒鸠姨。

第八次提交 到 第十一次 提交 都是 Guideline 4.3 - Design

Guideline 4.3 - Design

We noticed that your app provides the same feature set as other apps submitted to the App Store; it simply varies in content or language, which is considered a form of spam.    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 Design section of the [<u>App Store Review Guidelines</u>](https://developer.apple.com/app-store/review/guidelines/).  - Ensure your app is compliant with all sections of the [<u>App Store Review Guidelines</u>](https://developer.apple.com/app-store/review/guidelines/) and the [<u>Terms & Conditions</u>](https://developer.apple.com/terms/) of the Apple Developer Program.   - Once your app is fully compliant, resubmit your app for review.    When creating multiple apps where content is the only varying element, you should offer a single app to deliver differing content to customers. If you would like to offer this content for purchase, it would be appropriate to use the in-app purchase API.    Alternatively, you may consider creating a web app, which looks and behaves similar to a native app when the customer adds it to their Home screen. Refer to the [<u>Configuring Web Applications</u>](https://developer.apple.com/library/content/documentation/AppleApplications/Reference/SafariWebContent/ConfiguringWebApplications/ConfiguringWebApplications.html) section of the Safari Web Content Guide for more information.    Submitting apps designed to mislead or harm customers or evade the review process may result in the termination of your Apple Developer Program account. Review the [<u>Terms & Conditions</u>](https://developer.apple.com/terms/) of the Apple Developer Program to learn more about our policies regarding termination.    If you believe your app is compliant with the [<u>App Store Review Guidelines</u>](https://developer.apple.com/app-store/review/guidelines/), you may submit an appeal. Alternatively, you may provide additional details about your app by replying directly to this message.    Please see attached screenshot for details.

分析：

馬甲包問題 蘋果審核到 我們的APP與他人賬號(hào)上的某個(gè)APP（包括沒上線的，上線的淹真，移除的APP）有80%的相似度讶迁。

蘋果審核的包一直是1.0版本的包，我重寫項(xiàng)目后提交的包蘋果沒有審核到核蘸。后來蘋果電話聯(lián)系我巍糯，修改了屏幕截圖和版本號(hào)，重新提交APP客扎，才審核的最新的包祟峦。

解決：前面幾次修改工程名，類名徙鱼，方法名宅楞，資源圖片名，還是被拒。最后重寫了項(xiàng)目修改了80%以上的UI界面重新提交咱筛，修改了提交時(shí)候后的屏幕截圖及版本號(hào)終于解決了這個(gè)問題搓幌。

第十二次提交：

Guideline 2.1 - Performance - App Completeness

Your app or its metadata does not appear to include final content.     Before you submit your app to the App Store, all of its content and metadata must be final. Your app must not include placeholder or incomplete information. For example, an app with “l(fā)orem ipsum” text in the app description field will be rejected. Likewise, an app with placeholder screenshots, such as “screenshot coming soon,” will be rejected. Instead, you should only submit an app with complete information and content throughout.    Next Steps    To resolve this issue, please review your app and metadata to ensure that all of its content is final.

分析：您的應(yīng)用程序必須不包括占位符或不完整的信息，展示出來的商品迅箩，有包含測試商品

解決：后臺(tái)刪除測試數(shù)據(jù)溉愁。

第十三次提交，三個(gè)問題：Guideline 1.2 - Safety - User Generated Content 和 Guideline 2.1 - Performance - App Completeness

Guideline 1.2 - Safety - User Generated Content

Your app enables the display of user-generated content but does not have the proper precautions in place.    Next Steps    To resolve this issue, please revise your app to implement all of the following precautions:    - Require that users agree to terms (EULA) and these terms must make it clear that there is no tolerance for objectionable content or abusive users  - A method for filtering objectionable content  - A mechanism for users to flag objectionable content  - A mechanism for users to block abusive users  - The developer must act on objectionable content reports within 24 hours by removing the content and ejecting the user who provided the offending content

分析：

您的應(yīng)用程序支持顯示用戶生成的內(nèi)容饲趋，但沒有適當(dāng)?shù)念A(yù)防措施

-要求用戶同意條款(EULA)拐揭，而這些條款必須清楚表明，不會(huì)容忍令人反感的內(nèi)容或?yàn)E用用戶

-過濾不良內(nèi)容的方法

-一種用戶標(biāo)記不受歡迎內(nèi)容的機(jī)制

-一種機(jī)制奕塑，讓用戶阻止濫用用戶

-開發(fā)人員必須在24小時(shí)內(nèi)刪除令人反感的內(nèi)容報(bào)告堂污，并將提供違規(guī)內(nèi)容的用戶驅(qū)逐出境

解決：以上給出的五種辦法都要，添加相應(yīng)的功能龄砰。

1盟猖，注冊處添加用戶協(xié)議；’

2换棚，代碼或者后臺(tái)需要添加過濾不良內(nèi)容的代碼式镐；

3，添加舉報(bào)

4固蚤，添加拉黑或者加入黑名單（此次沒有添加拉黑娘汞，所以審核又一次被拒，下次加上了）

5夕玩，用戶發(fā)布內(nèi)容時(shí)候要提示用戶不能發(fā)布違規(guī)內(nèi)容和不良內(nèi)容你弦。、

Guideline 2.1 - Performance - App Completeness

We discovered one or more bugs in your app when reviewed on iPhone running iOS 12.2 on Wi-Fi.    Specifically, some content did not load properly.    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 [<u>Technical Note TN2431: App Testing Guide</u>](https://developer.apple.com/library/archive/technotes/tn2431/_index.html).     For a networking overview, please review [<u>About Networking</u>](https://developer.apple.com/library/archive/documentation/NetworkingInternetWeb/Conceptual/NetworkingOverview/Introduction/Introduction.html).

分析：在斷網(wǎng)情況下或者ipv6環(huán)境下燎孟，APP沒有數(shù)據(jù)禽作。

解決：在斷網(wǎng)時(shí)，提示網(wǎng)絡(luò)斷開缤弦，或者數(shù)據(jù)為空時(shí)领迈，提示沒有內(nèi)容；服務(wù)器添加支持ipv6碍沐；

Guideline 4.2.3 - Design - Minimum Functionality

We were required to install the WeChat app before we could log in via WeChat. Users should be able to log in with WeChat and access their accounts without having to install any additional apps.    Next Steps    If you would like to offer authentication through WeChat, please use a mechanism that allows users to log in with WeChat 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 [<u>What's New in Safari</u>](https://developer.apple.com/library/archive/releasenotes/General/WhatsNewInSafari/Introduction/Introduction.html) webpage.    Please see attached screenshots for details.

分析：們需要安裝微信應(yīng)用程序才能通過微信登錄狸捅。用戶應(yīng)該能夠使用微信登錄并訪問他們的帳戶，而不需要安裝任何額外的應(yīng)用程序累提。你的APP不能強(qiáng)制讓用戶安裝第三方軟件

解決：顯示的時(shí)候先判斷是否安裝了微信和QQ客戶端尘喝，如果安裝了，顯示第三方登錄按鈕斋陪，如果沒安裝不顯示朽褪。

第十四次提交：

Guideline 1.2 - Safety - User Generated Content

Your app enables the display of user-generated content but does not have the proper precautions in place.    Next Steps    To resolve this issue, please revise your app to implement all of the following precautions:    - A mechanism for users to block abusive users (黑名單 or 拉黑)

分析： 用戶阻止濫用的機(jī)制(黑名單或拉黑)

解決：需要添加 拉黑或者加入黑名單 機(jī)制置吓。

第十五次提交：

Guideline 2.1 - Performance - App Completeness

Your app crashed on iPhone running iOS 12.2 on WiFi when we:    Specifically, your app crashes when the user taps the 積分.    We have attached detailed crash logs to help troubleshoot this issue.    Next Steps    To resolve this issue, please revise your app and test it on a device to ensure that it runs as expected.    Resources    For information on how to symbolicate and read a crash log, please review [<u>Tech Note TN2151 Understanding and Analyzing Application Crash Reports</u>](https://developer.apple.com/library/archive/technotes/tn2151/_index.html).

分析：積分頁面，積分兌換記錄界面崩潰缔赠；

解決： 后臺(tái)數(shù)據(jù)返回為NULL,需要轉(zhuǎn)為字符串類型的數(shù)據(jù)衍锚，再展示出來。

值得一提的的是 馬甲包問題（4.3問題）嗤堰，審核時(shí)間會(huì)延遲戴质，一般是7到10天出結(jié)果，解決了這個(gè)問題其他的都是1到3天就出結(jié)果踢匣。