Reasons and solutions for uploading apps to Apple Store

One,Apps that is "demo", "Trial", or "test" versions would be rejected. Beta Apps May is submitted through TestFlight and must follow the TestFlight guidelines(any "beta", "demo", "Trial"), "try (t rial) "or" test "version of the app will be rejected. )

Reason: The app contains demo,trial,test, or beta, and does not comply with Apple's official audit conditions.

Solution: Check if the app contains the above words and delete them.

Another:If you would a-conduct beta trial for your app, your may wish to review the TestFlight beta testing Guide. If you had difficulty reproducing a reported issue, please try testing the workflow described in Technical q&a QA1764 : How to reproduce bugs reported against APP Store submissions. (If you want to publish a beta version, you'll need to publish it according to the TestFlight Beta release guide).

II, Apps must follow the IOS Data Storage guidelines or they would be rejected.

Reason: The app is not stored in accordance with Apple's official data storage scheme.

Solution:To check how much data your app is storing:
-Install and launch your app
-Go to Settings > ICloud > Storage > Manage Storage
-Select your device
-If necessary, tap "Show all Apps"
-Check Your app ' s storage

This is to examine how the data is stored in the project and to modify the data storage method of the app based on the iOS data store knowledge policy.

Report:

Data storage requirements:

1. only those user-generated documents or other data, or data that the app cannot recreate, should be stored in the /documents directory and automatically backed up to ICloud.

2. data that can be re-downloaded or generated should be stored in the /library/caches directory. For example, database cache files, downloadable files (magazines, newspapers, data used by map applications), etc. are in this category.

3. Temporary use of data should be stored in the/ tmp directory. Although these files will not be backed up by ICloud , the app will need to remember to delete the files after use so that it does not continue to occupy the user's device space.

4. use the do not backup property to specify files that need to remain on the device, even if there is low storage space. This property is required for those files that can be regenerated, but remain in low storage space, have an impact on the app's uptime, or if the user wants files to be available offline. This property can be used regardless of the file (including the Documents directory) in the directory. These files are not deleted and are not included in the user's ICloud or iTunes backup. Since these files always occupy the storage space of the user's device, it is the responsibility of the application to periodically monitor and delete these files.

III. Revise your app to complete, remove, or fully configure any partially implemented feature (s).

Cause: There are non-implemented functional modules in the project.

Solution: block or fully implement the functionality of the module that is not implemented. (Apple is estimated to be afraid of impacting the user experience.) ）

Four, 64-bit and iOS 8 requirements starts soon. Rejected statements are not included, roughly according to the February 2015 implementation of the mandatory support 64 for the system, this app does not meet the upload requirements.

Cause: A third-party library that supports 32-bit systems is used in the project, or an arm that supports 64-bit is not selected in the engineering configuration.

Workaround: Upgrade and modify all code and third-party libraries in your program that do not support 64-bit.

Attached: Detection method

1, the project is set to support iOS6 or even higher;

2, set architectures build to "standard architectures (includeing 64-bit)"

3, with 64-bit hardware for detection (real-machine debugging can detect a third-party library does not support 64-bit, and then upgrade or replace it)

4, set the project valid architectures:arm64,armv7,armv7s,

Archtectures:standard architectures (armv7,arm64)-$ (Archs_standard)).

Five, one of the most well-known is that in March 2015, the app that uploaded the Apple Store could no longer contain the words to check for updates, and Apple would automatically check for updates. Otherwise, being rejected is a very sad thing to do.

Many of these are binary data problems that need to be modified and re-packaged for uploading. The new app upload audit time is relatively long, once the audit, but will consume more time, so that opponents seize the opportunity, so hope to summarize the reasons for rejection and solutions, hope novice less go some detours!

Reasons and solutions for uploading apps to Apple Store