I am trying to submit my first application to the Mac App Store. I have setup the signing certificates on my computer, as well as setting up the application in iTunes connect. Xcode allows me to produce an archive of my app, and even export a signed pkg file. Both Application Loader and Xcode say that my binary passes "validation", but shortly after uploading my app to iTunes connect it is reported to have an "Invalid Binary." I read on Apple's iTunes Approval Process page some reasons why this might happen:
Appears when a binary is received through Application Loader, has been processed, but your binary is invalid. Examples of an invalid binary are: your binary icon does not meet our requirements, you have placed the payload directory at the wrong level in the .app wrapper, you attempted to use a non-increasing CFBundleVersion, etc.
Unfortunately I am not receiving an email when this error occurs, and nothing is telling me what the problem is. I am kind of hoping that Xcode would tell me if I signed my binary wrong in the "Validate" stage, but I may be wrong.
My question here is: 开发者_开发问答why might iTunes connect be reporting an "Invalid Binary" and how on earth can I fix it?
EDIT: I have taken some screenshots of my project's configuration settings, and of iTunes connect:
- iTunes connect app page
- Application in the Archive list
- Entitlements plist
- Code signing settings
- Info.plist
- Build settings (architectures, etc).
You most likely are trying to submit a build that has the same version number as an earlier build. All builds that you upload to iTunes connect must have different version numbers. For example: Joe submits his first build of his app to iTunes connect as version 1.0, next time he submits he must change the version to 1.1 or any other higher value.
精彩评论