在 Xcode 7中发现了意外的 Mach-O 头代码: 0x72613c21

小开

I had a same issue. I did a couple of things and my issue went away. I believe My issue was related to Cocoapods version but you can try couple of things here.

First clean DerivedData by:

1.Turn off Xcode

2.Go to ./Users/YourFile/Library/Developer/Xcode/DerivedData

3.Delete everything from this folder

4.Run Xcode

5.Build&Clean

Second for some reason, with latest cocoa pods version 0.39, I was getting following warning when I ran pod install

[!] The MY_TARTGET target overrides the EMBEDDED_CONTENT_CONTAINS_SWIFT build setting defined in `Pods/Target Support Files/Pods/Pods.release.xcconfig'. This can lead to problems with the CocoaPods installation

I've downgraded cocoapods by removing all installed cocoapods:

sudo gem uninstall cocoapods

then install older version:

sudo gem install cocoapods -v 0.38.1

This removed the warning and I was able to remove the error, "unexpected Mach-O header code: 0x72613c21"

小开

Double check Build Phases -> Copy Bundle Resources for a framework or other binary that shoundn't be there.

In my case, it was a 3rd party library (Parse) that I had added.

小开

In my case it was caused by change of Developer certificate/team.

I start project with personal Dev Apple ID and by the time I changed it to my work ID. When we try to export .xcarchive then "Match-O header" fail did appear. Nothing described here or at other sites don't change anything.

When I change Team back to my personal ID, error logs shows missing .xcent files for only few frameworks now (most recently added). So I start whole new project, paste all the sources and files, then run cocoapod and everything works as expect.

小开

Edit: This looks to be fixed in Xcode 8 Beta 3.

I'm currently experiencing this issue with Xcode 8 Beta 2 and Swift 3 with pure-swift Pods (which seems to be causing the issue).

Adding the following to my Podfile has fixed the problem.

post_install do |installer|
installer.pods_project.targets.each do |target|
target.build_configurations.each do |config|
config.build_settings['ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES'] = 'NO'
end
end
end

Credit goes to this comment by YuAo on GitHub.

小开

I had same issue in Xcode 8 beta 3. I fixed it removing Fabric and Crashlytics from Linked frameworks (Project => Target => General page) (source)

小开

I ran into this error with a FacebookSDK framework. I removed it from the Embed frameworks list in Build Phases and it solved the issue. Inspect the log and find the framework causing the error as mentioned by others.

小开

I had this problem with a manually-added PFFacebookUtils framework in a Swift 2.3 non-CocoaPods project. I fixed it by removing said framework from the embedded frameworks section of the "General" page of the build target and linked it in Build Phases -> Link Binary With Libraries

小开

Check two things for every framework:

The Mach-O type of the framework (in Build Settings of the framework target)

Whether you copy the framework by putting it in Build Phases -> Embed Frameworks (or Copy Bundle Resources as mentioned by a. brooks hollar)

If the Mach-O type of the framework is "static library", it should not be put in embed frameworks; if the Mach-O type is "dynamic library", it should be put in embed frameworks.

In my case it was SocketRocket I added manually which has both a static library target and a dynamic library target with the same framework name. After deleting the static library target and only embed the dynamic library framework, the problem disappears.

Note:

If you don't have access to the source project, you can manually check if it's a dynamic or static framework using this approach: https://stackoverflow.com/a/32591983/308315

小开

I encountered this issue in a very simple Framework project. I only had one target in my project for the framework and it was building fine. I wanted to add some unit tests, so I added two new targets: an iOS Unit Testing Bundle target, and a Single View Application target (to act as a host app for the tests). However, both new targets were throwing this error.

I discovered that the problem was caused by the Mach-O Type build setting on the new targets being set to Static Library. Apparently the new targets were inheriting the Mach-O type from the parent Project. When I set the Mach-O Type to the correct settings ("Bundle" for unit tests and "Executable" for the host app) it all worked! I also had to clean build, delete derived data and reset the simulator to get the new settings to take.

小开

In my case, I have a framework manually dragged into my project, and it is listed in General->Embedded Binaries, which cause error Found an unexpected Mach-O header code: 0x72613c21. After i moved it from Embedded Binaries to Linked Frameworks and Libraries, problem solved.

小开

I don't know why but somehow pods appeared to become an embedded binary. So I had to remove it, pod install once more, and the issue disappeared.

On Xcode 11 you need to change it to Do Not Embed in the Frameworks, Libraries, and Embedded Content.

小开

Take a look at this Apple documentation Embedding Frameworks in An App go to the section Embedded Static Libraries they explain this error like this:

This is caused by placing a static library in a bundle structure that looks like a framework; this packaging is sometimes referred to by third party framework developers as a static framework. Since the binary in these situations is a static library, apps cannot embed it in the app bundle.

They also provide a way to fixed:

you can solve this error by identifying the static framework and removing it from the Embedded Binaries section.

You accomplish this by following the instructions in Inspecting A Binary's Linkage

小开

Remove them from Embedded Binaries and add them to Linked Frameworks and Libaries, then Archive again and upload to store.

小开

For me, I had Fabric binaries in my Carthage /usr/local/bin/carthage copy-frameworks run script.

After removing those, it fixed the issue.

I'm using Xcode Version 9.4.1 (9F2000)

小开

My way of fixing this was to get back to Fabric/Crashlytics installation via Cocoapods instead of fancy Carthage setup (which appeared buggy).

小开

Given the amount of time I've poured into finding this problem, it was caused by Cocoapods. I was working on a Workspace that had both iOS apps and a command line tool to kick off some pipelines and stuff. My file looked like this:

target 'AppPipe' do
platform :osx, '10.14'
project 'AppPipe/AppPipe.xcodeproj'
pod 'Yams'


post_install do |installer|
installer.pods_project.targets.each do |target|
target.build_configurations.each do |config|
config.build_settings['MACH_O_TYPE'] = 'staticlib'
end
end
end
end

I thought the pods_install hook was local to the scope I was writing it in, but it wasn't! It actually turned all of my target's configs into staticlibs! This fixed it:

target 'AppPipe' do
platform :osx, '10.14'
project 'AppPipe/AppPipe.xcodeproj'
pod 'Yams'
end


post_install do |installer|
installer.pods_project.targets.each do |target|
target.build_configurations.each do |config|
# Only AppPipe always gets staticlib
if target.name == 'AppPipe'
config.build_settings['MACH_O_TYPE'] = 'staticlib'
end
end
end
end

小开

In XCode 11, click on the project file, select your target, then on General tab expand Frameworks, Libraries, and Embedded Content, change Embed & Sign to Do Not Embed.

小开

Check and looking for duplicate frameworks and Libraries in Link Binary With Libraries and Embed Frameworks in Build Phases tab of your project.

Only should be in one side ...

小开

If you have an Xcode project for a static framework, your test target must have "Bundle" value for MACH_O_TYPE build setting:

小开

When embedding bundles from library targets they may produce executables even with Mach-O Type = Bundle. So we can simply delete these executables from xcarchive (Products/Applications/APP_NAME/YourBundle.bundle/YourBundle)

小开

In my case in xcode 11, i resovle issue to set do not embeded in genral -> frameworks,libraies and embedded content

小开

One of the possible reason is nested framework.

Inspired by Golang, I recently refactored my project's code from:

App(with all the code in one target)

to ("->" means link with, ABCD means framework)

B -> C
A -> B


App -> A
App -> B
App -> C

It turns out that nested framework is not officially supported by Apple. So I had to flatten the dependency tree to:

App -> D


D -> A
D -> B
D -> C

小开

In my case, I selected the copy when installing and worked for me

小开

If you (potentially but not necessarily) used FirebaseSDK (especially Analytics) and get Mach-O error while running, archiving and uploading, try this:

Add this as a build post-actions script.

rm -rf "${TARGET_BUILD_DIR}/${TARGET_NAME}.app/Frameworks/FirebaseAnalytics.framework"
rm -rf "${TARGET_BUILD_DIR}/${TARGET_NAME}.app/Frameworks/GoogleAppMeasurement.framework"
rm -rf "${TARGET_BUILD_DIR}/${TARGET_NAME}.app/Frameworks/FIRAnalyticsConnector.framework"

if you added widgets and/or other plugin extensions add these lines as well:

rm -rf "${TARGET_BUILD_DIR}/${TARGET_NAME}.app/PlugIns/FirebaseAnalytics.framework"
rm -rf "${TARGET_BUILD_DIR}/${TARGET_NAME}.app/PlugIns/GoogleAppMeasurement.framework"
rm -rf "${TARGET_BUILD_DIR}/${TARGET_NAME}.app/PlugIns/FIRAnalyticsConnector.framework"

Brief explanation: The below quote is from the relevant discussion under https://github.com/firebase/firebase-ios-sdk/issues/6472 explains the reason behind this problem.

... so right now the firebase framework artifacts are being copied into the /Frameworks folder of the ipa and are embedded. The frameworks themselves are static frameworks.... If you delete them from the xcarchive manually, everything works as expected.

Basically many of the answers here point to the right direction, but the problem remains because the solution is to remove the unwanted artifacts every single time. Currently (Jan 2021) AFAIK there is no other way to solve it.

小开

Adding below script into Post-Actions of Archive helped me overcome this issue. It removes static-frameworks which are unrelated.

# https://github.com/firebase/firebase-ios-sdk/issues/6472
LOGFILE="${ARCHIVE_PATH}/static-frameworks.log"
echo "Removing static frameworks from ${WRAPPER_NAME} archive" > $LOGFILE
find "${ARCHIVE_PRODUCTS_PATH}/Applications/${WRAPPER_NAME}" -name '*.framework' -print0 | while IFS= read -r -d '' fm; do
name=$(basename "${fm}" .framework)
target="${fm}/${name}"
echo "Checking: ${fm}" >> $LOGFILE
if file "${target}" | grep -q "current ar archive"; then
rm -rf "${fm}"
echo "Removed static framework: ${fm}" >> $LOGFILE
fi
done

A comment from Firebase issue: https://github.com/firebase/firebase-ios-sdk/issues/6472#issuecomment-771351512

小开

Scheme->Edit Scheme->Archive->Post Action->Click '+' -> New Run Script Action-> paste below code

LOGFILE="${ARCHIVE_PATH}/static-frameworks.log"
echo "Removing static frameworks from ${WRAPPER_NAME} archive" > $LOGFILE
find "${ARCHIVE_PRODUCTS_PATH}/Applications/${WRAPPER_NAME}" -name '*.framework' -print0 | while IFS= read -r -d '' fm; do
name=$(basename "${fm}" .framework)
target="${fm}/${name}"
echo "Checking: ${fm}" >> $LOGFILE
if file "${target}" | grep -q "current ar archive"; then
rm -rf "${fm}"
echo "Removed static framework: ${fm}" >> $LOGFILE
fi
done

小开

Use this code as a script build-phase instead of a scheme post-build action. I found out of all the answers, this works the best:

# Fixes binary framework bug, see:
# https://developer.apple.com/documentation/xcode-release-notes/xcode-12_4-release-notes#Swift-Packages
# https://github.com/firebase/firebase-ios-sdk/issues/6472


echo "Removing static frameworks from ${TARGET_NAME}.app"
find "${BUILT_PRODUCTS_DIR}/${TARGET_NAME}.app/" -name '*.framework' -print0 | while IFS= read -r -d '' fm; do
name=$(basename "${fm}" .framework)
target="${fm}/${name}"
echo "Checking: ${fm}"
if file "${target}" | grep -q "current ar archive"; then
rm -rf "${fm}"
echo "Removed static framework: ${fm}"
fi
done

小开

2021! UPDATED

Here is the hack for this:

Build the app with the Pods_Runner.framework marked as Embed & Sign

Once it's built. Go to the same place and set the Pods_Runner.framework to Do Not Embed.

Go to Product -> Archive -> Submit the archive and it will all work as expected.

credits: lifenautjoe

小开

I encountered the same problem days ago, the root cause of this problem is:

** Some static libraries was wrongly embeded in the .app bundle. **

You can search .a or static .framework in the Products/*.app bundle in Xcode, and check out the project carefully, remove redundant static libraries.