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
Guideline 2.3.3 - Performance - Accurate Metadata
We noticed that your screenshots do not sufficiently reflect your app in use.
Specifically, your 5.8-inch iPhone X screenshots do not display the app in the correct device frame.
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.
Note that 5.8-inch display assets for iPhone X are optional and don't scale down to other devices sizes. Screenshots that include iPhone X layout features like rounded corners or sensor housing should only be used for the 5.8-inch display.
Resources
For resources on creating great screenshots for the App Store, you may want to review theApp Store Product Pageinformation 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 useMedia Managerto add custom screenshots for each display size and localization.
Guideline 2.4.1 - Performance - Hardware Compatibility
We noticed that your app did not run or display as expected when viewed on iPad running iOS 11.4.1.
Next Steps
To resolve this issue, please revise your app to ensure it runs as expected and displays properly at iPhone resolution on iPad. Even if your app was developed specifically for iPhone, users should still be able to use your app on iPad.
Resources
For information on iOS device screen sizes and resolutions, please review theiOS Human Interface Guidelinesas well as Points versus Pixels in theView Programming Guide for iOS.
You may also want to viewSize Classes and Core ComponentsandDefault Class Sizes for Different Devicesfor more information about designing apps for multiple screen sizes.
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.
Next Steps
While the payment system that you have included may conduct the transaction outside of the app, if the purchasable content, functionality, or services are intended to be used in the app, they must be purchased using in-app purchase, within the app - unless it is of the type referenced in guideline 3.1.3 of the App Store Review Guidelines.
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 App Store Connect, refer toApp Store Connect Help.
Guideline 3.1.1 - Business - Payments - In-App Purchase
We noticed that your app uses in-app purchase products to purchase credits or currencies that are not consumed within the app, which is not appropriate for the App Store.
Next Steps
To resolve this issue, please revise your app to ensure that the credits or currencies purchased with in-app purchase products are used within the app or remove the in-app purchases entirely.
Guideline 3.1.1 - Business - Payments - In-App Purchase
We noticed that your app allows users to "tip" the digital content creators in your app with a mechanism other than the in-app purchase API, which is not appropriate for the App Store.
Next Steps
To resolve this issue, please revise your app to use the in-app purchase API to pay for these sorts of transactions. Please note that whileguideline 3.2.1(vii)of the App Store Review Guidelines allows individual users to give a monetary gift to another individual user without using in-app purchase, that gift must not be connected to or associated at any point in time with receiving digital content or services.
While the payment system that you have included may conduct the transaction outside of the app, if the purchasable content, functionality, or services are intended to be consumed within the app, they must be purchased through in-app purchase - unless it is of the type referenced in guideline 3.1.3 of the App Store Review Guidelines.
Please see attached screenshots for details.
针对这些问题作出翻译
1:第一个问题是因为我们每天屏蔽其他用户发的东西
2:是因为程序没有适配ipad导致测试人员用ipad 登录都登录不了
3:是因为上传app的屏幕快照iPhone X的图片不对.
网友评论