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

app-store-connectapplication-loaderiosxcode

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

Best Answer

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.

enter image description here

Related Solutions

Ios – ERROR ITMS-9000: “Redundant Binary Upload. There already exists a binary upload with build version ‘1.0’ for train ‘1.0’”

More than one binary may be uploaded to App Store Connect for the same version, if the the Build number is increasing for each build uploaded to iTunesConnect. The build number just has to be unique (and higher) for each binary that is uploaded (select the Target, then Xcode -> General -> Build, see the picture below). For example in the image below the build uploaded has version 3.1.4 (3.75 in the older image) and the build number is 1. Thus, after uploading this image increase the build to a minimum 2 or higher. Then this binary may also be uploaded to App Store Connect as it's a later build according to the build number.

The version notes the release version of the app your releasing to the user. The build number remarks the final build of the binary uploaded to the store, i.e. after many bug fixes.

After Xcode 9 you are not able to upload a new build (for the same version), if there is a previous build with the same build number in the store. So, check your build number and increase if not certain.

EDIT: It's more correct to use 1, 2, 3, 4, etc. for the build number, but the version number has to be increasing, 1.0 -> 1.1 -> 1.2 etc. The build number has to be higher than what was submitted previously for the same version number, if not an error is posted. So, if a new binary is submitted that has version 3.75 and a build 1 has already been submitted, then next build shall be 2 or higher, but the version can still remain 3.75.

New updated and the recommended way of having the build numbers serial:

The older image to match the one below: Showing where to set the Build Version in XCode

After a new binary is uploaded and processed (~5-20 min processing time, if it doesn´t show up upload again and wait), then you can select the new binary and submit it for review. In the picture below you may see the old and the new binary listed in App Store Connect in the Build section of the current App version (you click the plus sign). Then the new binary is selected -> Saved -> Submit for Review. (Sometimes an error comes when submitting, then just try after a few mins or upload a new binary).

Showing list of binaries in iTunesConnect

For those inclined to do this automatically with an Xcode script, here is a description of making an automatic script for updating Build numbers Better way of incrementing build number?

R – Extend base template in Smarty

Although this question is a bit old, I thought that maybe someone looking for this information as of august 2011 would benefit to know that this can be done now with Smarty 3.

Example With Inheritance

layout.tpl

<html>
<head>
  <title>{block name=title}Default Page Title{/block}</title>
</head>
<body>
{block name=body}{/block}
</body>
</html>

mypage.tpl

{extends file="layout.tpl"}
{block name=title}My Page Title{/block}
{block name=body}My HTML Page Body goes here{/block}

output of mypage.tpl

<html>
<head>
  <title>My Page Title</title>
</head>
<body>
My HTML Page Body goes here
</body>
</html>

Taken verbatim from: http://www.smarty.net/inheritance

Best Answer

Related Solutions

Ios – ERROR ITMS-9000: “Redundant Binary Upload. There already exists a binary upload with build version ‘1.0’ for train ‘1.0’”

R – Extend base template in Smarty

Related Topic