Various ITMS errors when trying to submit archive

Question

So this is a weird one — I get the following errors when trying to submit my archive to the App Store:

ERROR ITMS-90049: "This bundle is invalid. The bundle identifier contains disallowed characters. [See the section of the Application Programming Guide entitled The APplication Bundle.]"

ERROR ITMS-90049 "This bundle is invalid. The bundle identifier contains disallowed characters

ERROR ITMS-90056: "This bundle is invalid. The Info.plist file is missing the required key: CFBundleVersion."

From my plist:

<key>CFBundleIdentifier</key>
<string>com.myApp.app</string>

…

<key>CFBundleVersion</key>
<string>3.1.5</string>

…

<key>CFBundleShortVersionString</key>
<string>3.1.4</string>

Running xCode 7.0.1

Answer 1

I'd like to expand an answer given by @silvon and link more keywords to this question.

Apparently, iTunes Connect backend now validates every single bundle shipped with your app. If a bundle contains Info.plist file, it must have CFBundleVersion and CFBundleShortVersionString keys.

So, if you are using any 3rd party frameworks (specifically, with Cocoapods), make sure that Info.plist in each framework bundle (if exists) contain these keys.

Answer 2

For all of you using CocoaPods, simply try to

pod update

In my case, it was a third party library loaded via cocoapods, but the update did the trick. BTW, none of the libraries had new versions, the update seems to repair some bad things too.

Answer 3

I solve this by following this link, add Bundle identifier which is missing in info.plist of TencentOpen SDK.

Answer 4

Check if the third-party's has plist file.Apple may mixed the third-party Sdk plist with the local plist file. Delete the third-party's plist file then upload success.

Answer 5

I did the same step as Silvon mention. Removed all third party lib's info.plist (pods as well) with xcode 6.4. Works for me.

Answer 6

There seems to be some Issues from Apples's Side, I am experiencing the same issues, I would suggest to wait for some time before making any major changes.

This seems to be happening a lot lately, after some time, It starts working again .