Found an unexpected Mach-O header code: 1918975009

[carloslozano]

Linked frameworks including invalid binaries. Builds work on device and emulator but non iOS binaries are being included in the build, causing the following validation error:

2014-11-19 22:00:57 +0000 [MT] Failed to generate distribution items with error: Error Domain=DVTMachOErrorDomain Code=1 "Found an unexpected Mach-O header code: 1918975009" UserInfo=0x7fb840744350 {NSLocalizedDescription=Found an unexpected Mach-O header code: 1918975009, NSLocalizedRecoverySuggestion=}

This makes it impossible to validate the application for distribution.

[carloslozano]

Fixed error by:

• Targeting iOS 8 on all embedded frameworks.
• Removing "Defines Module" from Build Settings.
• Realm, removed "phantom" framework (sourced from static lib)

It seems iOS < 8 targets with embedded frameworks are automatically rejected by the validation of the application... so they can't be distributed.

[carloslozano]

Targets < 8 no longer an issue 😅

[ainulyaqin]

Hi Carlos,

i have problem same with u, do you want to help me what the matter with this error ?

2015-04-20 10:15:02 +0000 [MT] Failed to generate distribution items with error: Error Domain=DVTMachOErrorDomain Code=1 "Found an unexpected Mach-O header code: 1918975009" UserInfo=0x7fe751d19ef0 {NSLocalizedDescription=Found an unexpected Mach-O header code: 1918975009, NSLocalizedRecoverySuggestion=}

using xcode 6.
base SDK project: 8.1
ios deployment target : target : 8.0

iam using cocoapod 0.36.x builder in myproject, i set to ios deplyment target 8.0 too,

in "Defines Module" set to "No"

I clean and archieve still show error when, export and save for ad hoc.

[carloslozano]

Are you trying to link against a static library from a Swift project?

I'm currently working on Xcode 6.3.1 and Cocoapods 0.36.4 and I'm no longer encountering this issue. However, I do recall that removing "Library Includes Swift Code" from the build settings of the project and this seemed to overcome the problem.

In any event, without looking at your specific use-case, it's a bit hard to determine the source of the problem. Is there any place where you have your code so that I can try to compile it with my current set-up and maybe find the offensive setting?

Regards,

C!