At the end of the year, all the apps in my hand will be launched. I don’t know if you feel the strict review team during this period. All the three projects in my hand have been blocked (three different accounts), two of which are iterations and one is a newly launched APP. ~~~~(>_<)~~~~ Let me summarize the problems I have encountered, hoping to help you in your confusion.
Guideline 2.3.3 – Performance – Accurate Metadata
We noticed that your screenshots do not sufficiently reflect your app in use. Please see attached screenshots for details. 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 down to other device sizes when viewed on the App Store in each territory. Resources For resources on creating great screenshots for the App Store, you may want to review the App Store Product Page information 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 use Media Manager to add custom screenshots for each display size and localization. Since your iTunes Connect status is Metadata Rejected, we do NOT require a new binary. To revise the metadata, Visit iTunes 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. NOTE: Please be sure to make any metadata changes to all app localizations by selecting each specific localization and making appropriate changes.
This problem is very simple that my screenshots can not reflect the main functions of my App, and then change the screenshots (I mainly cut several modules of my App)
Orthotropic 2.1 – Performance – App Displacement
We discovered one or more bugs in your app when reviewed on iPad running iOS 11.2.5 on Wi-Fi connected to an IPv6 network. Specifically, the In-App Purchase (IAP) results in an error. Below are the steps to reproduce the issue: 1. Launch the application 2. Navigate to Purchase/Recharge tab 3. Proceed to purchase one of the IAP products 4. IAP confirmation window appears 5. Confirm Purchase 6. IAP results in an error The review was conducted under sandbox environment. 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. 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.
This question is written very clearly, said to be on the IPad IPv6 network when the payment is not successful, always failed to pay
When I received this email, I immediately made a test, simulated IPv6 network and tested it with iPhone and iPad, and found that the in-app purchase was completely ok, but the in-app purchase callback was a little slow on iPad. Then I took a screenshot and told them that the in-app purchase could be completed without any problems after the test. Then I waited for their response that night. They usually reply after 1pm (it was 8am at that time) and then get an email in the evening saying that the in-app purchase was still no good, with the same screenshots. Then I wondered, how could it be like this? How could they always fail to pay when there was no problem? Suddenly I found a problem: Did they test the payment using sandbox test account? Because my app is new and the in-project purchase project has not been approved, if I don’t use the sandbox test account, I will definitely fail to buy the app. Don’t they use the sandbox test account? No way! I don’t believe they are so stupid, but I have no other way to deal with it. After ######, I replied to them by email that my in-app purchase project had not been reviewed and the in-app purchase test had to be conducted with sandbox account. Then I recorded a video and uploaded it to YouTube to prove that in-app purchase could be completed on IPad. Then, after a long day of waiting, I got an email from Apple in the evening:
Hello, Thank you for your response. We will continue to review your app, and will notify you if there are any further issues. Best regards, App Store Review
Say thank you for your reply, and we will continue to review your App. (To be honest, I was not happy when I received this email. I thought they were getting tired of us replying too many times. Is this about suspending my App? Want to pass pass however however bai, what call continue to examine and verify, difficult way is this the delay in legendary examine and verify?) At that time, a little worried to sleep… But the next day I suddenly you found that it had passed! Happy I jumped up in the subway!
This problem summed up, if you really have no problem on the bold to argue, although the audit has become very strict but no problem is no problem, you can record video screenshots to prove their innocence 😝
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. Resources To Learn more about requesting the user’s permission to access app features, visit the iOS Human Interface Guidelines. 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.
The problem is that we use camera permissions in the project, but we don’t tell the user where to use this permission
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. 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 In-App Purchase 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. 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. 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 iTunes Connect, refer to In-App Purchase for Developers.
This is that my App with the purchase of other third-party payment (in fact, we made a contact switch), the problem is more serious, the audit team said directly to your project to accelerating, next audit time is not long, this kind of question if you are prepared to do so, preferably not now, this card is very strict recently, heavy punishment. Had better be honest to remove the third party payment into the purchase!
Guideline 5.1.1 – Legal – Privacy – Data Collection and Storage
We noticed that your app requests the user’s consent to access the Location services 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 Location services. Resources To learn more about requesting the user’s permission To access app features, visit the iOS Human Interface Guidelines. 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.
The problem is that we used location and didn’t say where we used location and didn’t say in permissions. But we didn’t use location, we didn’t use the word “see” in our app, and we got confused, so I emailed back and told them that we didn’t use location and we never used it. Then they emailed back saying ok, you can move on to other questions….. (There are other problems with the above in-app purchase). Well, I don’t know how to capture this image, I suspect it’s from another app!
Guideline 4.2.3 – Design-Minimum Functionality
We were required to install the QQ app before we could log in via QQ. Users should be able to log in with QQ and access their accounts without having to install any additional apps. Next Steps If you would like to offer authentication through QQ, please use a mechanism that allows users to log in with QQ 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 What’s New in Safari webpage.
Qq third-party login must be installed QQ, hope not to install QQ can also be used, processing method is to support the web page QQ login
Guideline 5.1.1 – Legal – Privacy – Data Collection and Storage We noticed that your app requires users to register with personal information to purchase non account-based in-app purchase products, which does not comply with the App Store Review Guidelines. Please see attached screenshot for details. Apps cannot require user registration prior to allowing access to app content and features that are not associated specifically to the user. Next Steps User registration that requires the sharing of personal information must be optional or tied to account-specific functionality. To resolve this issue, please make it clear to the user that registering will enable them to access the content from any of their iOS devices, and to provide them a way to register at any time, if they wish to later extend access to additional iOS devices.
We note that your App requires users to register their personal information in order to purchase non-account based in-app purchases, which do not comply with the App Store Review Guidelines. I met this problem once before in another App. At that time, I remember I sent an email to explain that our App must be logged in to purchase goods, because our goods must rely on the account number of what….. Of course, if you think it is clear, you can try it. If not, you should honestly change it to allow tourists to buy goods. It is better to store purchase records according to iCoud for cross-device use.
Guideline 2.1 – Information Needed
This type of app has been identified as one that may violate one or more of the following App Store Review Guidelines. Specifically, these types of apps often: 1.1.6 – Include false information, features, Or misleading metadata. 2.3.0 – Undergo significant concept changes after Approval 2.3.1 – Have hidden or undocumented features, Including hidden “switches” that redirect to a gambling or lottery website 3.1.1 – Use payment mechanisms other than In-app purchase to unlock features or functionality in the app 4.3.0 – Are a duplicate of another app or Are Tenber similar to another app 5.2.1 – Were not submitted by the legal entity that owns and is responsible for Offering any services provided by the app 5.3.4 – Do not have the necessary licensing and permissions for all the locations where the app is used Before we can continue with our review, please confirm that this app does not violate any of the above guidelines. You may reply to this message in Resolution Center or the App Review Information section in iTunes Connect to verify this App’s Compliance. Given the tendency for apps of this type to violate the aforementioned guidelines, this review will take additional time. If at any time we discover that this app is in violation of these guidelines, the app will be rejected and removed from the App Store, and it may result in the termination of your Apple Developer Program account.
This problem may be one of the ultimate boss that has been exposed recently. Directly say that the application will be deleted or even banned if the problem occurs again in the next submission. I was shocked to see this. So many questions….. It turned out that many people had received the email. And many apps receive this without violating any of the above. It is enough to prove that receiving this email does not mean that you have all the above problems, you should check each item by yourself, if not, you can reply to the email (it is known that some people replied to the email saying that they did not have the above problems and also passed the audit), of course, this should be handled according to your own project situation. But one thing is for sure: if you have a problem and have received this email, you need to take care of it, because you have probably already been targeted, and the next submission will be taken seriously.