Download lists failed please contact the developer

Knowing the culprit files often narrows down a solution. Use the following two options to identify which files are the culprit:.

More often than not there is logging to be found in the device's console that gives a coherent reason for the failure, or, a substantial clue that can be used to extrapolate the cause. Logging that is relevant to Watch App installation failures is found in the paired phone's device console. Click the down triangle button at the bottom-middle of the screen to bring up the console logging. Use the device console as follows to isolate logging messages that pertain to the installation failure:.

This is a general installation failure whereby a development or beta test app is attempting to install on an iOS device whose UDID is not contained in the app's embedded provisioning profile. Paired watch UDIDs are displayed in a section titled Paired Watch Information. Sync profile according to section: If Xcode does not show the Paired Watch Information section, restart Xcode.

The error is often caused by misconfigured target or code signing settings. Follow these steps to troubleshoot the issue:. Follow the standard installation Troubleshooting Process. Targeted device family related install failures.

If console logging accompanies your installation failure regarding obsolete resource rules paths you must use the following steps to resolve the issue. Set the Code Signing Resource Rules Path build setting at all targets to a blank value.

This is a broad type of error whereby an app is attempting to install onto a device type that is not compatible with its list of supported devices defined in its info. Inspect Setting the Target iOS Devices for correctness. As another example, watch apps must have a UIDeviceFamily value of '4' which indicate it is allowed download lists failed please contact the developer install on Apple Watch.

Review the entitlements of the embedded provisioning profile in each bundle the app and its plugins in order to confirm the expected entitlements are present: Analyze all entitlement sources and destinations according to the steps in guide TN - Code Signing Entitlements Troubleshooting. Warnings about missing application-identifier entitlements appearing in your console may pertain to remedies provided in this section. These can occur in iOS 8. This indicates that the app being installed did not have the application-identifier entitlement.

The OS console logging that results during this type of installation failure provides more information than that displayed in Xcode when this error stops a run. Use the steps in section Extract errors from the device console to find that helpful logging which usually includes the culprit files. Use the Terminal command in section Analyze binaries in built products step 4 to check bundles for corruption.

This document assists with iOS App installation failures. Use it to diagnose specific causes and resolve app installation failures. This document is intended to help developers resolve installation failures of development or beta test builds that are installed through Xcode or iTunes. Users who are experiencing installation failure of App Store apps. Instead you should contact iTunes Store Customer Support for assistance.

If for example, a built binary remains signed by an old provisioning profile, try doing a clean build. TN iOS Code Signing Troubleshooting. Terms of Use Privacy Policy Updated: To submit a product bug or enhancement request, please visit the Bug Reporter page. Please read Apple's Unsolicited Idea Submission Policy before you send us your feedback. Guides and Sample Code Developer Search. Installation Failure Troubleshooting for iOS PDF Companion File.

Troubleshooting Process Extract errors from the device console. List of Installation Error Messages Application Verification Failed. Could not download lists failed please contact the developer executable.

Check the resulting console logging from top to bottom being sure to thoroughly analyze each line. Check installation download lists failed please contact the developer error messages you might find against the List of Installation Error Messages covered in this document. This is an error that occurs when attempting to run a newly installed watch app.

Check the name and entitlements embedded in this profile using the command covered in section: To resolve it, follow this process:. Restart Xcode after installing profiles or making other code signing changes.

Architecture related installation failures. Watch App bundle ID doesn't match the bundle ID expected by the Watch Extension. Entitlement related installation failures. Ensure the application signature is not corrupt using the process covered in section: Check the bundle signature for corruption. This error indicates that an App Store distribution provisioning profile was mistakenly used to sign the Ad Hoc build.

For example, you must ensure the watch extension Architectures build setting is set to Standard 64bit. See iOS only App Size of the iTunes Connect Developer Guide to ensure your app is within the size limits. Ensure that your UIRequiredDeviceCapabilities Info. For example, requiring "armv7" will prevent your app from installing on iPhone 3G or earlier download lists failed please contact the developer that use the armv6 architecture.

Please note that builds signed with an App Store distribution provisioning profile cannot be installed onto development or testing iOS Devices; they can only download lists failed please contact the developer submitted to iTunes Connect for App Review. To resolve this issue, sign the app with an Ad Hoc distribution provisioning profile instead. Following the steps for modern day code signing demonstrated by the following guide resolves this issue in every case.

You must remove the watch target from your project and recreate it with the current version of Xcode in order to correct this problem. This is a broad type of error download lists failed please contact the developer an app is attempting to install on an older version download lists failed please contact the developer the OS that is not supported according to the app's deployment target Info.

Installation failure of the watch app accompanied by invalid info dictionary device console logging indicates that there is an invalid key or syntax error in the watch app's Info.

The watch extension keeps a reference of its corresponding watch app within its Info. The property key is: If your error message is not covered here, continue to the Supporting Information section of this guide. Find the built bundles in Xcode's project files pane. Expand the Products section to reveal the apps. Control-click the phone app and choose Show in Finder. Do not analyze the watch extension and watch app that reside in the root built products folder; these are only copies of the actual bundles that are sent to the device for installation and running which reside in the phone app.

Thank you for providing feedback! Your input helps improve our developer documentation. How helpful is this document? How can we improve this document? Fix typos or links Fix incorrect information Add or update code samples Add or update illustrations Add information about

Reattempt your app build and installation while making sure to code sign using the desired profile. Add a previous-application-identifiers entitlement to a code signing entitlements file for your app. Example format of this entitlement follows:. Request a special provisioning profile from Developer Programs that will also contain the above entitlement. Both steps are needed in order to successfully install development or beta test builds on top of an existing install that contains a different App ID prefix.

The resolution of this installation error depends on whether you intend on changing the App ID prefix of your live app in the App Store. If you do not intend on changing your App ID prefix, this error is simply an indication that Xcode has chosen the download lists failed please contact the developer provisioning profile to code sign your app.

This can be resolved by adding the application-identifier entitlement to the app through use of a custom Code Signing Entitlements file.

My error isn't listed! Supporting Information Analyze binaries in built products. Paired Watch Information section does not show in Xcode's Devices window. Signer identity does not match across app and its additional signed frameworks or plugins. Entitlements are not valid. Upgrade's application-identifier entitlement string [ Please try submitting your feedback later.

Restarting Xcode is sometimes needed to straighten out Xcode's knowledge of code signing certificates and profiles. Therefore, try restarting Xcode if a recent code signing change is not taking effect. Doing a clean build is sometimes needed for certain code signing download lists failed please contact the developer to take effect.

If while analyzing the built watch binary via the steps in Analyze binaries in built products you find that the watch app's UIDeviceFamily is not '4', the watch target in your Xcode project was created in an early beta version of Xcode.

Warnings about your application-identifier entitlement string not matching your installed application-identifier string appearing in your console when trying to install download lists failed please contact the developer upgrade may pertain to this section.

See Setting the Deployment Target and ensure this value is less than or equal to the version of iOS installed on the target device. For example, Apple Watch apps currently require a deployment target of iOS 8. To resolve this problem:. This error message stops a run attempt and indicates that a corrupt signature was detected on one or more signed bundles associated with the install. This problem occurs when the OS validates a bundle before installation and determines download lists failed please contact the developer one or more files have been inserted, modified or removed from a bundle after it was code signed; the OS rejects such binaries as a security measure.

Developers who are experiencing download lists failed please contact the developer failure of App Store apps should instead contact App Store Developer Support through iTunes Connect.

There are additional causes of this problem covered in Download lists failed please contact the developer Watch Information section does not show in Xcode's Devices window. An example error message printed to the device console in entitlement related installation failures is:. As a general rule, prune your code signing entitlements plists to just those entitlements Xcode writes into this file as a result of configuration that is done on target Capabilities tabs. If your app contains additional plugins such today or watch extensions, verify that entitlements match across the iOS app and its extensions using the following steps:.

Download lists failed please contact the developer a clean build after installing profiles or making other code signing changes. Once again, Analyze binaries in built products. Check bundles for corruption using the steps in section: If Xcode does not show the Paired Watch Information, perform the following steps:. Install all newly created or updated provisioning profile into Xcode by doing one of the following:. Drag and drop the. Repeat the process of checking for bundle corruption on any signed frameworks or plugins your bundle may optionally contain.

You should also be aware of the potential consequences of changing the prefix of a live app in the store. The following document covers this topic in detail: QA - Resolving the Potential Loss of Keychain Access warning.

Follow these steps to resolve the issue:. Optionally double check the App ID Prefix on the downloaded profile using the Terminal command in: How do I check the entitlements associated to my Provisioning Profile?

Be sure to check only the bundles that are in the documented hierarchy, and include all bundles that have been signed. This is a broad type of installation failure whereby an app is attempting to install on an OS which does not support any architecture provided by the app. See Setting Architectures for iOS Apps to ensure your app includes architectures required by the target device.

Server configuration troubleshooting for Over The Air OTA install failures are not covered here. Use this guide as a reference if the install failure persists through Xcode or iTunes. If the install failure is not reproducible through Xcode or iTunes you should instead contact AppleCare for Enterprise Deployment or Download lists failed please contact the developer Integration support depending on your needs. Use the following process to troubleshoot installation failures that occur during Xcode run attempts or installation of beta test builds through Xcode or iTunes.

Signer identity related installation failures. Device UDID missing from provisioning profile related install failures. Application is missing the application-identifier entitlement. Upgrade's application-identifier does not match the installed app. Device Console logging 'invalid info dictionary'. Deployment target related install failures. A signed resource has been modified or deleted. App size related installation failures. UIRequiredDeviceCapabilities related installation download lists failed please contact the developer. Resource rules path related installation failures.