最近准备上架一个项目，主要是针对公司的入库数量、溯源、任务量统计、销售报表等功能，有地理位置、推送等功能，如下图，从7月23日开始提交第一个版本，到今天（9.6）终于上架了，期间被拒了接近10次，我也是醉了。
下面总结一下，这些被拒的重要原因：
1.Guideline 2.5.1 - Performance - Software Requirements
Thank you for your resubmission. However, we noticed that the previous issue has not been resolved.
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.
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.
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.
Guideline 3.2 - Business
We found that your app is not appropriate for the World storefront because it is a custom app designed specifically for 百维, whose users are in China.
At this time, China is not part of the Volume Purchase Program.
Next Steps
Please revise your app to set the storefront to China.
Resources
You can find additional information regarding the Volume Purchase Program and the Custom B2B Store in App Store Connect Developer Help.
Please see attached screenshot for details.
Since your App Store Connect status is Rejected, a new binary will be required.
解决方案：这个操作是用户扫描二维码的用处， 虽然加上了用户访问，但是由于弹框内容不合理，所以悲剧了
2.During review, your app installed or launched executable code, which is not permitted on the App Store. Specifically, your app uses the itms-services URL scheme to install an app.
Please note that while educational apps designed to teach, develop, or allow students to test executable code may, in limited circumstances, download code, such code may not be used for other purposes and such apps must make the source code completely viewable and editable by the user.
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 Software Requirements 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.
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 Terms & Conditions of the Apple Developer Program to learn more about our policies regarding termination.
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.
Guideline 4.0 - Design
Your app includes an update button or alerts the user to update the app, but the update button or alert does not link directly to the app’s page on the App Store.
Next Steps
To resolve this issue, please ensure that tapping the update button takes the user directly to the app’s page on the App Store to update the app.
Guideline 3.2 - Business
We found that your app is an in-house app, intended for employees or members of your organization. As such, it is not appropriate for the App Store.
For information on distributing proprietary, in-house apps, please refer to the Apple Developer Enterprise Program.
解决方案：由于我们公司的app是对内部员工使用，所以被拒，你发一个邮件，说明app不仅仅是对内部员工使用的就可以了
3.We discovered one or more bugs in your app when reviewed on iPhone running iOS 11.4.1 on Wi-Fi.
Specifically, your app displayed an error message after we tapped on the 登录 button.
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.
Please see attached screenshots for details.
解决方案:即使你的项目只是用在iphone上，不用再pad上，但是也是要兼容pad的，后来我兼容了一下pad，就可以了
4.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.
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.
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.
解决方案：这是我的app内部有跳转到浏览器的功能，但是如果用“prefs:root=”会被拒，用苹果的另一个方法实现跳转页面既可以了
新增问题：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
Please see attached screenshots for details.
解决方案：这种情况，一般是有类似发朋友圈的功能，只要能添加举报、后台删除截图、用户协议就可以了，如果你的产品确实没有什么可添加的，你也可以直接回复苹果审核员，说明是安全的，也有可能下个版本就过了
5.Guideline 2.1 - Performance - App Completeness
Your app or its metadata does not appear to include final content. Specifically, your app description contains placeholder 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 “lorem 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.
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.
你的项目中应该是有按钮功能没有实现，或者不完善或者写的假的数据之类的，把这些功能完善或者去除掉，重新提交一个版本应该就可以了
持续更新中。。。。。。
