App submits itunes Connect, "binary invalid" problem solution.

Yesterday submitted the package submission app, will be uploaded to itunes Connect, think it can be released, then click Build version, found no just uploaded package, so click on "pre-release" to see, will see "uploaded", and then refresh once again to see, it becomes the binary invalid, incomparably depressed, Uploaded five or six times is a binary file invalid,

Reason: 1. Since February 2015, the newly uploaded app uploaded to itunes must support 64-bit, the new upload means the first upload,

Or not approved, in short, in the AppStore above the app is not on the shelves, must support 64-bit, including the code inside the project and the use of static library files

2. If the previous itunes above has approved the app, now just upload upgrade version, update version to review, this can also be submitted successfully, itunes above verify that the binary files can be passed,

Do not have to support 64-bit, but don't be happy too early, this is only expedient, to June 2015 upload the upgrade version or to support 64-bit, but now this situation does not need to force,

Personal advice or as soon as possible to check their own code and static library, need to replace the early replacement, was refused to wait time is usually about 2 weeks, very not worth

Don't say much nonsense, now let's talk about the solution!

1. Check to see if 64-bit support is supported (64-bit for published apps)

As shown in support for 64-bit

2. See if the schemes analyze and archive are release modes

Analyze to release mode

The above two resolved or not, the package upload TMD or binary file is invalid, why?

When using Xcode to pack and upload, Apple lets us tick the include app symbols for your application to receive symbolicated crash logs from Apple by default.

The tick is removed, but it still cannot be uploaded or the binary file is invalid. Continue to solve the problem

Architectures: The set of instructions you want to support. (The support instruction set is implemented by compiling the corresponding binary packets, and if there are multiple supported instruction sets, the packets containing multiple instruction set codes will be compiled, resulting in a large package that is eventually compiled.) ）

Valid architectures: The set of instructions that will be compiled. (Valid architectures and architecture the intersection of two collections is the version generated by the final compilation)

Build Active Architecture only: Compiles only the set of instructions that are applicable to the current device (if this parameter is set to Yes, using iphone 6 debugging, then a binary that is eventually generated that supports the ARM64 instruction set. General in debug mode set to Yes,release to No).

It's also best to pack in an iOS device environment and not plug in a real machine.

In order to be rigorous can export the package, and then check the terminal to see if support arm64,

App submits itunes Connect, "binary invalid" problem solution.