Trouble uploading app to iTunes Connect

hank863 · 03-13-2009, 04:59 PM

I've uploaded an application to iTunes Connect before, but right now I keep getting this error:

Quote:

The binary you uploaded was invalid. The application-identifier entitlement is not formatted correctly; it should contain your 10-character App ID Seed, followed by a dot, followed by your bundle identifier.

Can you please tell me where this "application-identifier" is and give me an example of what it should look like?

c0der · 03-13-2009, 06:11 PM

This is all clearly explained in step-by-step detail in the dev portal section of the apple dev site. In fact, when you login, there's a link at the right top of the screen about submitting your app to the app store.

You need to do more reading, but basically the application identifer is set in the project info section in xcode. It's generally in the format: "com.website.<appname>"

Again, this is all clearly explained (step-by-step) in the website documentation. Take a few minutes to read it and you'll understand what to do.

hank863 · 03-13-2009, 06:13 PM

Thank you, but I have read that and have used the EXACT same configuration to build and submit this IDENTICAL app before. I'm going to keep working on it, but nothing's changed.

amro · 03-14-2009, 11:55 PM

Quote:

Originally Posted by hank863

Thank you, but I have read that and have used the EXACT same configuration to build and submit this IDENTICAL app before. I'm going to keep working on it, but nothing's changed.

I have the exact same problem -- can't figure it out.

Edit: FYI I renamed my zip to have a space in it, uploaded and it failed (purposely to get it to clear state). I renamed the same zip w/ out a space uploaded, it gave some generic error, I hit home, went back in and uploaded the zip again and it worked. O.o

zacware · 03-15-2009, 12:16 AM

well, for me it's usually an error about a missing icon.png, but myself as well as several others I've talked with have had the problem magically disappear after force quitting the finder and re-zipping the file

another time I removed and readded my entitlements.plist file

yes I know it does sound logical at all, but I've had times where I've tried 7 times in a row to upload and then by doing one of the above things it magically worked.

Quote:

Originally Posted by hank863

I've uploaded an application to iTunes Connect before, but right now I keep getting this error:

Can you please tell me where this "application-identifier" is and give me an example of what it should look like?

Scuba · 03-15-2009, 12:21 AM

Quote:

Originally Posted by amro

I have the exact same problem -- can't figure it out.

Edit: FYI I renamed my zip to have a space in it, uploaded and it failed (purposely to get it to clear state). I renamed the same zip w/ out a space uploaded, it gave some generic error, I hit home, went back in and uploaded the zip again and it worked. O.o

Yes, spaces = bad

Sometimes I need to restart xcode or my whole comp for a build to work for upload. Make sure you clean before you build. If you kept your old app version archived you can copy it's plist to the new one just to make sure you didn't bump something somewhere accidentally.

I've actually never changed a bundle identifier. Partially because I don't fully understand them (at least how they interact with a [wildcard] application id and what purpose they server), and also because since I haven't and had no problems I see no need to.

But even though it ways it should contain your 10 character app id, I read in the docs recently that has been changed. You don't want it in there and xcode handles that for you. Maybe that's your problem if you added it yourself before and the app uploaded. Now, if you've updated to a newer xcode since then, it could be duplicating it. I donno, just a thought - this whole area is a nightmare for me :P

I just keep at it and then when it randomly works _slowly_back_away_

amro · 03-15-2009, 12:23 AM

Quote:

Originally Posted by Scuba

Yes, spaces = bad

...

Yup, what I mean is I knew the spaces would cause it to bomb out, but I thought their webapp was storing some bad state, causing a change or two to fail to be picked up, so I just put the space in hoping it would bomb completely, then tried normally and it worked. I really have no idea if it impacted it or not -- I just know I tried uploading for an hour and it finally worked with no actual change to my project at all..

hank863 · 03-15-2009, 12:35 AM

I encountered a lot of weird problems uploading recently. I ended up completely redoing everything regarding App IDs and Provisioning Profiles and it worked.

iRick.ca · 04-06-2010, 07:15 PM

Quote:

Originally Posted by Scuba

I just keep at it and then when it randomly works _slowly_back_away_

I think this is the most relevant explanation out there. For each person who says "RTFM" it works perfectly, there are at least 2 people experiencing pseudo-random confusion.

My success seems to be a combination of doing something the 3rd (or 20th) time, with random "Clean all targets" thrown in through XCode.

Great when it works, crap when in the frustration mode.

autoalert · 06-24-2010, 09:25 AM

After trying many different things including the random approach I think i've finally hit upon the answer

It seems that Apple now require you to add the following lines into entitlements.plist. Before I only had the get-task-allow key.

Code:

	<key>application-identifier</key>
	<string>9M234HNM4D.com.autoalert.appname</string>
	<key>get-task-allow</key>
	<false/>
	<key>keychain-access-groups</key>
	<array>
		<string>9M234HNM4D.com.autoalert.appname</string>
	</array>

Where the number is taken from the appid in the provision profile section of the iPhone Provision portal (no this is not our real id ;-)) and the rest is what is in the identifier field in Xcode, (click on target, get info and then properties tab)

Hope that helps

Richard

coder19 · 06-30-2010, 01:55 PM

I had the same problem. You have to delete your old Entitlements file, and create a new one:
File > New File > (iPhone OS) Code Signing > Entitlements

Of course, Apple doesn't mention this at all. They leave it for frustrated developers to figure out by scouring message boards.

NickVellios · 07-01-2010, 11:44 PM

Quote:

Originally Posted by coder19

I had the same problem. You have to delete your old Entitlements file, and create a new one:
File > New File > (iPhone OS) Code Signing > Entitlements

Of course, Apple doesn't mention this at all. They leave it for frustrated developers to figure out by scouring message boards.

Apple is getting absolutely ridiculous with this crap. When is it going to stop? They are making app developers run through an undocumented ever-changing maze of bullshit.

LunarMoon · 07-02-2010, 02:44 AM

I agree totally! Apple docs is like going to a library where all books are dumped on the hall with no order, no labels, no one to help.

justdan0227 · 07-06-2010, 10:24 AM

Quote:

Originally Posted by coder19

I had the same problem. You have to delete your old Entitlements file, and create a new one:
File > New File > (iPhone OS) Code Signing > Entitlements

Of course, Apple doesn't mention this at all. They leave it for frustrated developers to figure out by scouring message boards.

Thanks for the info!!! That worked!

pieter78 · 07-07-2010, 05:10 AM

Quote:

Originally Posted by coder19

I had the same problem. You have to delete your old Entitlements file, and create a new one:
File > New File > (iPhone OS) Code Signing > Entitlements

Of course, Apple doesn't mention this at all. They leave it for frustrated developers to figure out by scouring message boards.

Thanks a million... this also solved my frustrations!
(at least, part of them

)

Pieter

ianian · 07-26-2010, 02:57 PM

Oh Apple... Why do you do this to us....

Thanks coder19, this worked a treat.

burniejm · 08-03-2010, 10:12 AM

Quote:

Originally Posted by coder19

I had the same problem. You have to delete your old Entitlements file, and create a new one:
File > New File > (iPhone OS) Code Signing > Entitlements

Of course, Apple doesn't mention this at all. They leave it for frustrated developers to figure out by scouring message boards.

Wow... that was frustrating... having to use the app loader now is a pain!

nexirius · 08-04-2010, 06:59 PM

I guess I have the same problems as you guys! What do I have to put
into my Entitlement.plist? Nothing, just create it?

I can't get it working yet...

pieter78 · 08-05-2010, 03:35 AM

Quote:

Originally Posted by nexirius

I guess I have the same problems as you guys! What do I have to put
into my Entitlement.plist? Nothing, just create it?

I can't get it working yet...

Just create it. The SDK will fill it with a different content, and then you can just recompile.

nexirius · 08-05-2010, 09:18 AM

Quote:

Originally Posted by pieter78

Just create it. The SDK will fill it with a different content, and then you can just recompile.

Somehow it worked. Yesterday it didn't. I guess it was some weird bug of
XCode, it always told me "Uknown Error" when bulding. After a clean
reboot it suddenly worked.

I just have to say, this stuff really "could" **** people off. Why can't they
just make a built in uploader in XCode where you can directly Build+Upload?

I hope it doesn't get more complicated in XCode 4, but I guess another 5
hours can be planned for the new version.

whoisdis · 08-26-2010, 08:50 PM

Restarting computer and re-building, zipping and uploading worked for me.

StevenD · 09-20-2011, 12:38 AM

Quote:

Originally Posted by autoalert

After trying many different things including the random approach I think i've finally hit upon the answer

It seems that Apple now require you to add the following lines into entitlements.plist. Before I only had the get-task-allow key.

Code:

	<key>application-identifier</key>
	<string>9M234HNM4D.com.autoalert.appname</string>
	<key>get-task-allow</key>
	<false/>
	<key>keychain-access-groups</key>
	<array>
		<string>9M234HNM4D.com.autoalert.appname</string>
	</array>

Where the number is taken from the appid in the provision profile section of the iPhone Provision portal (no this is not our real id ;-)) and the rest is what is in the identifier field in Xcode, (click on target, get info and then properties tab)

Hope that helps

Richard

That worked for me. It wouldn't allow MYTENDIGIT.*, but rather MYTENDIGIT.bundle-identifier. Don't forget to re-archive it before trying to submit again.
/SD

sierra · 09-22-2011, 09:38 PM

I just went through this issue with XCODE 4 giving this same error during the distribution build:

"The binary you uploaded was invalid. The application-identifier entitlement is not formatted correctly; it should contain your 10-character App ID Seed, followed by a dot, followed by your bundle identifier."

Your advice on adding the two key-pairs in the entitlements file worked! Don't know how much longer this woulda taken me otherwise - thanks!

Quote:

Originally Posted by autoalert

After trying many different things including the random approach I think i've finally hit upon the answer

It seems that Apple now require you to add the following lines into entitlements.plist. Before I only had the get-task-allow key.

Code:

	<key>application-identifier</key>
	<string>9M234HNM4D.com.autoalert.appname</string>
	<key>get-task-allow</key>
	<false/>
	<key>keychain-access-groups</key>
	<array>
		<string>9M234HNM4D.com.autoalert.appname</string>
	</array>

Where the number is taken from the appid in the provision profile section of the iPhone Provision portal (no this is not our real id ;-)) and the rest is what is in the identifier field in Xcode, (click on target, get info and then properties tab)

Hope that helps

Richard