Submit App Store Considerations 1

1. The Apple iOS app data storage guidelines are not adhered to.

This is especially important if your app has offline data download capabilities. Because offline data generally occupy a large amount of storage space, can be re-downloaded and rebuilt, but users often want to keep the system storage space is still properly exist, will not be automatically cleaned up by the iOS system. Therefore, it cannot be placed in the/library/caches directory (this directory may be purged by the iOS system when the system is in tight space). It can only be placed in the home directory/documents or the home directory/library/the custom folder, so that the iOS system will not be automatically cleaned out. However, these data can be very large, if placed in the home directory/documents or home directory/library/Custom folder, will be Icoud automatic synchronization, then users need to sync a lot of traffic, Apple may therefore reject your app shelves. Therefore, you need to set the "Do not backup" property to the custom directory in your program.

The points to note about data storage are summarized below:

Key data

Content: User-created data files that cannot be recreated automatically after deletion

Path: Home directory/documents

Management: iOS systems are not purged when they are running out of storage space and are backed up to itunes or icloud

Cache data

Content: can be used for offline environment, can be repeated download duplicate generation, even when offline, the application itself can run normally

Path: Home directory/library/caches

Management: Empty in case of insufficient storage space, and will not be automatically backed up to itunes and icloud

Temporary data

Content: Files that are temporarily generated for an internal operation when the app is run

Path: Home Directory/tmp

Management: May be purged by iOS system at any time, and will not be automatically backed up to itunes and icloud, try to empty the files when they are no longer in use, and avoid wasting on user device space.

Offline data

Content: Similar to cached data, it can be re-downloaded and rebuilt, but users often expect that the data will not be automatically deleted by the system even when storage is tight

Directory: Home directory/documents or home directory/library/custom Folder

Management: Similar to key data, even if the storage space is not clear, the application should clear the unused files, so as not to waste user device space. You need to set "do not back up to Icoud", otherwise it will be audited.

2. No test account provided

If your app has some features that need to be logged in to use, then you need to submit a review, tick the demo account, and provide the corresponding information, such as:

Now many apps in order to be more convenient and fast, to prevent users to forget the password, the use of mobile phone number + verification code Way, so there is no way to provide Apple demo account, unless the account system to provide support to modify the background. In this case, there is no need to tick the demo account, but in the notes with Apple to explain, said we are also to enhance the user experience, so the account system has been improved, the user has a mobile phone can login, do not need to register what, such as. If you don't say anything, just wait to be rejected.

3. The app used with related hardware does not provide demo video.

This refers to hardware that does not require MFI authentication via BLE (low power Bluetooth) or Wi-Fi connected hardware. Directly in the notes to provide relevant features of the demo video, such as.

The demo video needs to include a full connection process operation and a hardware-related presentation after the hardware is connected. I can see my "Pants Treasure" demo video directly on Youku. So it's not like the rumor that you need to put FQ on YouTube, just put Youku Tudou or Baidu online. Also do not need to use English, in Chinese can.

4, the use of the relevant hardware with the app, did not provide ppid. (Product Plan ID)

If your app needs to interact with the MFI-certified hardware, using the EA Framework (externalaccessory.framework), configure the Protocol string (supported external accessory protocols), Then you need to provide ppid in the memo message.

Many times, our app can fit many models of hardware at the same time, each model of hardware corresponding to the ppid is different. What if a new model of hardware support is added to the AppStore after it has been submitted for approval? Do you need to send a separate version to add up the corresponding ppid? The answer is no, because the app support Ppid list information is placed in the memo information, the new ppid to the list does not need to modify the binary file information, Apple is also more humane here, you can not submit a new version of the case to increase ppid information.

5, the use of background location services, but did not specify why

Apps that used the background targeting feature only need to be configured in Info.plist Required background Modes-app registers for location updates You can. But from 2016 onwards Apple suddenly asked if the app to use the positioning function, in addition to the program to do the configuration, but also need to explicitly tell the user in the interface what your background positioning is to do, otherwise you will receive a message similar to the following.

1.1-apps using background location services must provide a reason that clarifies the purpose of the use, using mechanism s described in the Human Interface guidelines.

To modify it can also be simple, depending on your app needs to be configured in Info.plist, nslocationalwaysusagedescription or nslocationwheninuseusagedescription field description. Such as

6. The screen shot uploaded is too far from the app's specific use of screenshots

The screenshot feature provided by AppStore is intended for users to have an intuitive understanding of the app's functionality and what the interface might look like when not downloaded. So Apple also allows developers to do some landscaping on screen screenshots, not necessarily the original screenshot.  But there is a limit, that is not too far apart, the specific scale of Apple did not give a quantitative standard. The company project has a large version on-line a relatively large new features, in order to highlight this feature, the designer redesigned a very Q version of the functional demonstration. The results were uploaded and told by Apple that the screenshot did not match the app's functionality.

These are I in AppStore Audit personally stepped on some pits, of course, there are many pits, my team and I have noticed so efforts to avoid, but personally think also very need to pay attention to, I simply listed below for your reference.

• Discovered using an undisclosed API

• Use and system-close icons

• The interface is too ugly or too complex to interact with.

• Unstable, prone to collapse

• Too similar to other apps on the app market

• Detection Update in App

• A third-party operating system name or icon appears

• Insufficient testing, compatibility issues with some app claims supported operating system versions

We have said so many trampled pits, or almost stepped on the pit, nothing more than to be in the future app development as far as possible to avoid. Here are some of my experience summary for your reference.

1. Prevention of the preceding

The ability to plan for a product manager first needs to be judged whether it is technically achievable, or if it is implemented without the use of nonpublic APIs. Because a lot of times, even if you through the function of dynamic splicing and other technical means in the submission of the audit to avoid API scanning, but also inevitably by Apple from the function of discovery or by competitors report. Then the interaction design and the UI need to have their own judgment, the interface can not be too ugly, the interaction can not be too complex, can not use the icon that is too similar to the system.

2, before the release of the checklist

Each project needs to precipitate the checklist before the release, the pit before stepping on the memo, but also through the network information and other means to understand the most recent time rejected some of the main reasons, may be related to their own app notes, and then before the release of the page by check again.

3, pre-submit AppStore Audit

If also prevent, the hair version before also checklist, but sometimes it is inevitable hundred dense a sparse have omitted, especially the new features more version. I would like to highlight here is the pre-submission AppStore audit. The version of the project has a release period, generally in the first week or so before the release of the app version basically stable, but also need to modify some bugs and regression test. This time you can submit a version to AppStore to audit, anyway, the version number is not used, as long as the product manager does not occupy the version number on the line. What are the benefits of pre-submission audits?

(1) can help expose potential problems.

This version may have developed some new features, and then some places might not have taken into account the audit-related risks. If waiting for the project to end the official release of the exposure, it is a regret.

(2) In the case of necessity, you can test the boundaries of Apple.

Apple audit terms In fact there are many times there is no quantitative standard, such as screen shots can not be used when the application is not too far away from the screen, to get the UI designer to give screenshots, we sometimes have no way to determine whether it really conforms to Apple's specifications, but it does not matter, Let's start by submitting a version to try it out, and then again, for example, Apple asked for the app to be submitted after June 1 to support Ipv6-only's network. But for historical reasons, there is a third-party SDK in the project, and they have no way to provide a new version of support IPV6 before our release. Then I look at the internet also shared that Apple is not very strict with this requirement, just need to iOS9 under the main function can support IPV6 on the line. Of course, as the project leader, certainly can not say directly to this function cut off, also or credulous Netizen said ignore risk. What do we do? Please pre-submit a version and try to make a decision. The result is that it can be audited, so the final version does not cut off this feature, guaranteeing the integrity of the product on-line.

4, about AppStore expedited audit

If you have been rejected by the previous effort, or if the app is released to catch up with a certain time node, there is too little time reserved for app audits for a variety of reasons. This time you need to use the expedited audit channel to Apple.

You search for iOS expedited audit in Baidu, you will find a lot of claims can help you quickly review the person, 24 hours through the audit, review the payment after the pass, do not pass the money. If you do not know that Apple has an official expedited audit function, you are easily fooled by these empty glove white wolves, and the charges are 5000RMB start. Then I really want to say to you, find me, give you friendship price 50 percent.

How does Apple's expedited audit work? On the Itunesconnect page, click "?" in the top right corner. icon, select "Contact Us" in the pop-up menu,

Then on the Contact Us page, select "App Review", "app Store Review", "Request expedited Review",

Finally, fill in the form with relevant information, the most important of which is the reason why you need urgent review. Usually write to catch a major festival operation node, or emergency repair a serious flash back problem, and then note the flashback phenomenon of the detailed steps to reproduce, you can.

Regarding the specific expedited audit there is no limit, the number of times is related to the app or with the Development Account, Apple has no official instructions. But to be sure, online rumors only two times a year the opportunity for expedited review is not correct. But in order to make good steel use in the blade, or use this function with caution, in case there is really need for expedited audit but not respond.

From the first half of this year, the app audit time has been greatly shortened, generally do not need to use this feature.

Submit App Store Considerations 1