Getting ERROR ITMS-9000 when trying to upload an app using Application Loader

Question

When I try to upload an application to iTunes Connect using application loader, I get these errors:

Apple's web service operation was not successful

Unable to authenticate the package: (app id).itmsp

ERROR ITMS-9000: "Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, value 'development' for key 'aps-environment' in 'Payload/brainademy.app/brainademy' is not supported." at SoftwareAssets/SoftwareAsset (MZItmspSoftwareAssetPackage)

This has been happening for about 36 hours, and Apple support tells me to try again in 30 minutes (which obviously doesn't work).

I'm using the latest versions of both Xcode and application loader, I'm building using a physical iPhone, and I have the archive set to release. When I click Activity... Everything works fine, and then I see:

ERROR ITMS-9000: "Invalid Code Signing Entitlement...

Then everything works fine again, until I see

An error occurred talking to the iTunes Store

Answer 1

Your app states that you are using a Push Development entitlement. Only (Push) Production entitlements may be used to send an app to Apple. Review your certificates (inside developer.apple.com - certificates) and locate a certificate that states:

If you do not need that certificate, just click on the certificate and revoke it. If you need the development certificate, it means that what you need is to generate the Production APNS certificate.

Answer 2

I got one because my XCode loves to play a joke on me with Code Signing Identity section in Build Settings. For Release it should be iOS Distribution, not iOS Developer. Sometimes it resets.

Answer 3

For anyone else that may be getting this error:

in Target > Info I changed my "Executable File" name and it threw this error. Just leaving it alone I find is best.

Answer 4

This just happened to me. The problem was simply that my production provisioning profile had expired, and XCode for some reason decided to use the development profile. Regenerating a new production provisioning profile fixed the problem.

Answer 5

With newer versions of Xcode, this is no longer a problem

---

lnjuanj found the answer, yet there's also something else like this that could happen when your exporting an application that happened to me multiple times.

When your exporting your archive, make sure to check save as Enterprise Ad Hoc Deployment, not Submit to iOS app store, which is the default. Then, open up Application loader, and select the .ipa file that XCode generated.