05-01
2. 1 Performance: App Completeness
5. 1.1 Legal: Privacy - Data Collection and Storage
5. 1.2 Legal: Privacy - Data Use and Sharing
### Guideline 2.1 - Information Needed
We have started the review of your app, but we are not able to continue because we need additional information about your app.
**Next Steps**
To help us proceed with the review of your app, please provide detailed information to the following questions. The more information you can provide upfront, the sooner we can complete your review.
**- What are the correlation between information such as national ID, national ID number, educational background and current address with phone recycling?
- What is the correlation of credit score and selling of mobile device?**
### 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.
We have attached a screenshot of the error message displayed when we attempted to sign in.
**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 iTunes 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 iTunes 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.
If your iTunes Connect status shows as Metadata Rejected, we do not require a new binary to correct this issue. Please reply to this message in Resolution Center to confirm the availability of a valid demo account, and we will continue with the review.
### Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage
We noticed that your app requests the user’s consent to access their contact information 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 user's contact information.
**Resources**
To learn more about requesting the user’s permission to access app features, visit the [iOS Human Interface Guidelines](https://developer.apple.com/ios/human-interface-guidelines/app-architecture/requesting-permission/). You may also want to review the [Technical Q&A QA1937: Resolving the Privacy-Sensitive Data App Rejection](https://developer.apple.com/library/content/qa/qa1937/_index.html) page for details on how to provide a usage description for permission request alerts.
### Guideline 5.1.2 - Legal - Privacy - Data Use and Sharing
Your app accesses user data from the device but does not have the required precautions in place.
**Next Steps**
To collect personal data with your app, you must make it clear to the user that their personal data will be uploaded to your server and you must obtain the user's consent before the data is uploaded. You must also have a Privacy Policy URL and ensure that the URL you provide directs users to your privacy policy.
- Starting with iOS 6, there are keys for specifying the reason the app will access the user's protected data. When the access prompt is displayed, the purpose specified in these keys is displayed in that dialog box. If your app will be transmitting protected user data, the usage string in your access request should clearly inform the user that their data will be uploaded to your server if they consent.
05-02
### Guideline 2.1 - Information Needed
We have started the review of your app, but we are not able to continue because we need additional information about your app.
**Next Steps**
To help us proceed with the review of your app, please provide detailed information to the following questions. The more information you can provide upfront, the sooner we can complete your review.
**- What are the correlation between information such as national ID, national ID number, educational background, martial status and current address with phone recycling?
- What is the correlation of credit score and selling of mobile device?
- What is the purpose of requesting contact information?**
### Guideline 2.5.13 - Performance - Software Requirements
We noticed that your app includes facial recognition for account authentication but uses a facial recognition technology other than LocalAuthentication.
**Next Steps**
To resolve this issue, please revise your app to use LocalAuthentication for any account authentication based on facial recognition.
**Resources**
Visit Apple Developer for resources on [using LocalAuthentication](https://developer.apple.com/documentation/localauthentication) to request authentication from users.
### Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage
We noticed that your app requests the user’s consent to access their camera and contact information 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 user's camera and contact information.
**Resources**
To learn more about requesting the user’s permission to access app features, visit the [iOS Human Interface Guidelines](https://developer.apple.com/ios/human-interface-guidelines/app-architecture/requesting-permission/). You may also want to review the [Technical Q&A QA1937: Resolving the Privacy-Sensitive Data App Rejection](https://developer.apple.com/library/content/qa/qa1937/_index.html) page for details on how to provide a usage description for permission request alerts.
### Guideline 5.1.2 - Legal - Privacy - Data Use and Sharing
Your app accesses user data from the device but does not have the required precautions in place.
**Next Steps**
To collect personal data with your app, you must make it clear to the user that their personal data will be uploaded to your server and you must obtain the user's consent before the data is uploaded. You must also have a Privacy Policy URL and ensure that the URL you provide directs users to your privacy policy.
- Starting with iOS 6, there are keys for specifying the reason the app will access the user's protected data. When the access prompt is displayed, the purpose specified in these keys is displayed in that dialog box. If your app will be transmitting protected user data, the usage string in your access request should clearly inform the user that their data will be uploaded to your server if they consent.
05-07
2. 1 Performance: App Completeness
2. 5 Performance: Software Requirements
5. 1.1 Legal: Privacy - Data Collection and Storage
5. 1.2 Legal: Privacy - Data Use and Sharing
Hello,
Regarding 2.5.13, to resolve this issue, please revise your app to use LocalAuthentication for any account authentication based on facial recognition. Alternatively, please remove all references to facial recognition to avoid confusion.
Regarding 5.1.2, the Privacy Policy URL does not directs users to privacy policy page.
To resolve this issue, please ensure the Privacy Policy URL is directed to intended destination.
Upon further review, we found that your app does not comply with the following guidelines:
**Guideline 2.1 - Performance - App Completeness**
We discovered one or more bugs in your app when reviewed on iPhone running iOS 11.3.1 on Wi-Fi connected to an IPv6 network.
Specifically, the app was unable to load camera after tap on photo upload tab.
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](https://developer.apple.com/library/content/technotes/tn2431/_index.html).
For a networking overview, please review [About Networking](https://developer.apple.com/library/content/documentation/NetworkingInternetWeb/Conceptual/NetworkingOverview/Introduction/Introduction.html). For a more specific overview of App Review’s IPv6 requirements, please review the [IPv6 and App Review](https://forums.developer.apple.com/message/147579#147579)discussion on the Apple Developer Forum.
Best regards,
App Store Review
解决方案：
001
在解决方案中心，及时回复苹果审核团队的邮件。要及时，态度也要良好。现在苹果审核反馈很快。所以他们需要什么，你就及时提供什么就可以。
002
要制作在ipv6环境下的运行视频，这是他们那边的运行环境。如果他们发现了bug，比如在某个系统下无法运行“ We discovered one or more bugs in your app when reviewed on iPhone running iOS 11.3.1 on Wi-Fi connected to an IPv6 network.”重新制作一个在这个特殊环境下运行的视频就可以。
003
Guideline 2.1 - Information Needed
以及下面这些：
"Specifically, the app was unable to load camera after tap on photo upload tab."
苹果审核团队对于app的业务逻辑并不清楚，所以可以在解决方案中心回复，告知具体的业务逻辑。
004
- 1.1 Legal: Privacy - Data Collection and Storage
- 1.2 Legal: Privacy - Data Use and Sharing
在涉及用户隐私权限这一块，首先：提示信息：要指名：访问相机干什么？访问通讯录干什么？
还有必须让用户知道app对其信息进行保护。
比如5.1.1，这个问题，返回提到。而且反馈的截图一直在访问通讯录那边。所以我们加一个了用户隐私协议。并在通讯录这边，用户可以访问到该协议。
005
Guideline 2.5.13 - Performance - Software Requirements
We noticed that your app includes facial recognition for account authentication but uses a facial recognition technology other than LocalAuthentication.
如果项目要用到人脸识别，苹果要求必须使用localAuthentication 进行识别，所以要么替换成苹果的人脸识别sdk，要么不要使用该功能。
006
涉及到用户隐私这一块，苹果审核很严，这一块需要做的：权限的提示明确，加隐私协议。
007
在提交市场的时候，虽然隐私政策网址是可选项，但是建议必填指向用户隐私协议即可。
008
我们的app从5月1号第一次被拒，到今天5.8，中间被拒3次，发送反馈邮件5封，一直持续反馈，终于成功上线。所以多点耐心，及时反馈，都会解决的。