- 2 Safety: User Generated Content
- 1 Performance: App Completeness
- 5 Performance: Software Requirements
- 1.1 Legal: Privacy - Data Collection and Storage
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.
Although your application contains a flagging mechanism (舉報(bào)), it does not contain a user blocking mechanism (黑名單/拉黑).
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
原因：APP里有舉報(bào)功能，但是沒(méi)有加入黑名單功能
解決：增加了加入黑名單功能
Guideline 2.1 - Information Needed
We have started the review of your app, but we are not able to continue because we need access to a video that demonstrates the current version of your app in use on a physical iOS device, pairing and interacting with the designated hardware.
Please ensure the video you provide shows a physical iOS device (not a simulator).
Next Steps
To help us proceed with the review of your app, please provide us with a link to a demo video in the App Review Information section of App Store Connect and reply to this message in Resolution Center.
To provide a link to a demo video:
- 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 "App Review Information"
- Provide demo video access details in the "Notes" section
- Once you've completed all changes, click the "Save" button at the top of the Version Information page.
原因：APP里有與物理設(shè)備交互的功能界轩，但是蘋果方無(wú)設(shè)備無(wú)法完成測(cè)試
解決：錄制視頻預(yù)覽上傳
Guideline 2.5.1 - Performance - Software Requirements
Your app uses the "prefs:root=" non-public URL scheme, which is a private entity. 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.
Continuing to use or conceal non-public APIs in future submissions of this app may result in the termination of your Apple Developer account, as well as removal of all associated apps from the App Store.
Next Steps
To resolve this issue, please revise your app to provide the associated functionality using public APIs or remove the functionality using the "prefs:root" or "App-Prefs:root" URL scheme.
If there are no alternatives for providing the functionality your app requires, you can file an enhancement request.
原因：APP里有使用prefs:root=的非公有URL schema
解決：全局搜索prefs:root=汗菜，找到替換方案
Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage
We noticed that your app requests the user’s consent to access their camera, photos, microphone, and location 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, photos, microphone, and location.
To help users understand why your app is requesting access to their personal data, all permission request alerts in your app should specify how your app will use the requested feature.
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 screenshots for details.
原因：Info.plist中對(duì)使用權(quán)限的配置未標(biāo)明具體使用的場(chǎng)景情況
解決：對(duì)應(yīng)的Value值詳細(xì)的描述使用的場(chǎng)景
另外秆吵，上傳的APP截圖要跟對(duì)應(yīng)機(jī)型一樣亏掀，如圖上邊有設(shè)備的邊框要跟對(duì)應(yīng)尺寸的設(shè)備一致
