Common App Rejection Reasons and Responses for Resolution Center

Rejection Reason #1

We found that your app exhibited one or more bugs, when reviewed on iPad running iOS 5.1.1, on both Wi-Fi and cellular networks, which is not in compliance with the App Store Review Guidelines.

Specifically, your application loads to an empty storefront. Please refer to the attached screen shot for more information.

This is due to a lack of content/published content, or public content.

Action to take:

Locate the publication in Publish.

Assume the user, org or publication

Check if there is any issue there. If there is an issue, go into the issue screen, check if the content has been marked as published. Check if the availability is back dated (or now). Check that the issue is not marked as private. If there is no issue there. Some sample content will need to be created and uploaded. Make sure that the issue is available, public and set to the correct cost (paid or free).

Install the app to your device if possible, check that you can see the issue in the Download screen and that the product price (or free tag) resolves without an error.

Respond with:

Once you have made sure that the issue is correct and available for Apple to review, respond and tell them that everything has been resolved on the server and that they should be able to review the application again successfully.

Rejection Reason #2

We found that your app exhibited one or more bugs, when reviewed on iPad 2 running iOS 5.1.1, on both Wi-Fi and cellular networks, which is not in compliance with the App Store Review Guidelines.

Specifically, the user is unable to view app content since the activity indicator spins indefinitely after launch. A screenshot of this issue has been provided for your reference.

This is due to a very difficult bug to recreate and debug in bookmode apps. It seems to be as rare as once per device. A background thread gets locked which means the app tries to load indefinitely.

Action to take:

Add the response to the resolution centre first

Then mark the binary as ready to upload again

You can upload the same binary again - as the bug will never happen on that device again and just hope the same reviewer looks at the app.

This is also a good time to up the version of the app to the latest version if possible.

Respond with:Tell them that you have resolved the issue and that you are uploading a new binary for review now.

Rejection Reason #3

It is required to revise the app to include the mechanism to allow user to sign up for the free subscription. For more information, please see Newsstand for Developers for information on Newsstand Kit.

The free subscription does not appear if the product id has not been copied over from iTC to the app settings in Publishing Center.

Respond with: Apologise, and tell them that closing and opening the app and reviewing again, they should see that product to review.

Rejection Reason #4

Your app has the UIFileSharingEnabled key set to true in the Info.plist, but this feature is not functional. When file sharing is enabled, the entire Documents folder is used for file sharing. Files that that are not intended for user access via the file sharing feature should be stored in another part of your application's bundle. If your application does not require the file sharing feature, the UIFileSharingEnabled key in the Info.plist should not be set to true.

Respond with:

We require UIFileSharingEnabled because we allow many file formats to be side loaded and viewed in the application, like png, pdfs, zip files etc. This feature is predominately used by the content creators. This allows them to add the content that they have designed for the application and test its functionality on device and in a live environment during the production phase before sending it live to users.

The content that is side loaded into the documents directory is then moved to comply with iCloud storage requirements.

During the content creation phase our designers side load content via iTunes into the application for testing purposes. To do this our application is available for File Sharing in the applications tab in iTunes. Once synced, the app provides the user with a warning popup, tapping proceed will allow the app to install the sample content which can then be viewed and tested to ensure that it is functioning correctly.

This content testing phase is done on device as we have found that having the ability to test content on all devices, rather than just in the simulator, allows us to create quality content that runs as expected across the different devices and iOS. We have found many features that appear to work in simulator but don't actually work on device which is why it is important for us to be able to test on device.

Please let us know if you require any further information.

Rejection Reason #5

We found that your app includes URLs which do not properly navigate to the intended destination, which is not in compliance with the App Store Review Guidelines. Privacy URL registered in iTunes Connect, http://www.wrongwebsiteaddress.com, is not directly linked to the Privacy Policy web page. It would be appropriate to ensure all URLs properly resolve to the appropriate destinations before resubmitting your binary.

Action to take:

This means that the Privacy Policy URL you have provided is incorrect. Log into iTunes Connect, click on your app and then find the Privacy Policy URL field. Update the Privacy Policy URL to the direct link of the Privacy section of your website, then reply via Resolution Centre informing Apple that you have done so.