May 1, 2017 | au editor The review of the Apple App is a big obstacle. It is normal to meet the rejection. If it is rejected, it is based on the feedback question and the following ideas are provided to find a solution. Apple’s audit is roughly divided into three parts: pre-approval, machine audit, and manual audit. iOS App App Store Refused to Submit Review Tutorial After the ipa package is uploaded, the first thing to enter is the pre-qualification, which will be scanned by the API. After the pre-approval, the build version will appear at the https://itunesconnect.apple.com/ background event, and then the audit will be submitted (if not, there will be Feedback e-mail, check the reasons, a lot of upload ipa success, but did not see the ipa build version backstage, it is not pre-trial.) At the beginning of submitting the audit, it shows that the stage (waiting for review) is generally a machine audit. The machine audit is mainly used to perform machine audit on the code and check whether the APP is repeatedly applied. The “2.1 Apple Dog Year of the Year package” event is more dependent on the machine to automatically audit. , reduce labor costs; After passing through, it will be displayed as (auditing) this stage, ie, the manual review stage. This stage mainly looks at the metadata of the App, such as the APP cover, functions, experience, etc., and pays attention to the user experience. By this step, there will soon be results. Now. At present, the mechanism for the examination of the machine has become more and more perfect, and it has also received more and more attention. Compared with the previous months, the time of the recent Apple auditing has gradually shortened and the average audit time is 23.9 hours. 2.1 App Completion There are very obvious bugs such as application crashes, load failures, etc., applications that do not support IPv6 networks, test account numbers, and hidden switches. Solution: Test the product in advance for bugs, whether it can be used under the IPV6 network, etc. According to feedback e-mails, one by one review the compliance of their own product information, and if appropriate, send screenshots to the Apple official to prove their innocence. 2.3 Accurate metadata Mainly application titles, descriptions, screenshots, etc. are inconsistent with the application function. If you use Android phone screenshots, browser screenshots! Solution: Replace the screenshots again to ensure that the entire APP functionality and processes look consistent. Remove obfuscated module code or obfuscated the code that needs to hide functionality and redirect link URLs to increase logic complexity. 3.2.1 Acceptable Business Model Mainly no qualifications. Solution: The best solution is to get qualifications. If you really don’t have qualifications, it is recommended that you send as much evidence of your company’s compliance as possible to Apple, and use shells and new accounts to try your luck. try. 5.1.1 Data Collection and Storage It is mainly the App that enforces user registration and collects/shares user’s personal information implicitly based on functions that do not require user information. Solution: First negotiate with the user, let the user agree to register, the “strong landing” function must be modified to prompt the landing version. 4.3 Duplicate App Mainly for the duplicate App, is the vest bag. Solution: You can fix this by changing the name, icon, main tone, code, etc., and note that the same vest bag is submitted at least one day apart. 4.2 Minimum functional requirements The main problem lies in the fact that Apple thinks that some developers have insufficient apps for uploading their apps, or they don’t have their own core features. For example, directly packaging a web page on a shelf can easily trigger this problem. Solution: You can add some feature-rich products (navigation bar, drop-down refresh, push notification, etc.). If you think that the function is complete, you haven’t passed the audit. You can explain to Apple the user needs of the product and the display of specific functions. 3.1.1 Purchase Project Mainly access to third-party payment, Alipay, WeChat and so on. Solution: Take honestly the payment method paid by Apple and use in-app purchase. If you hide the virtual product or change the payment method after you pass it, there is a certain risk. 2.5 Software Requirements The main product is added to the violation code Solution: It is possible that the three-party library contains the SDK, you can update all three-party libraries, or decompile the submitted ipa, check the document for any violation of the string, and then delete it. 5.1.5 Positioning Service The main reason is that the App has not been allowed to share the collected user data with a third party, and does not specify the purpose of use. For example: location, account number… Solution: If you want to take user data information, you need to give the user prompts, and get the user’s permission, or set to optional, and clearly inform Apple collection of user data information purposes. In general, it is to pop up a prompt explaining what to do with this permission and write it clearly. 5.2 Intellectual Property It is mainly the unauthorized use of copyrighted third-party materials and App that may not be similar to Apple’s existing products. Workaround: Make sure the app only contains content that you create or own a license to use, submits the product using written evidence from a copyrighted third party, or hides portions of the product that are not authorized by a third party. The audit will also encounter a variety of issues and make corresponding changes based on feedback.