• The first thing you should make sure is that your static library has all architectures. When you do alipo -info myStaticLibrary.a on terminal - you should seearmv7 armv7s i386 x86_64 arm64 architectures for your fat binary.

• To accomplish that, I am assuming that you're making a universal binary - add the following to your architecture settings of static library project -

• So, you can see that I have to manually set theStandard architectures (including 64-bit) (armv7, armv7s, arm64) of the static library project.

• Alternatively, since the normal$ARCHS_STANDARD now includes 64-bit. You can also do$(ARCHS_STANDARD) andarmv7s. Checklipo -info without it, and you'll figure out the missing architectures. Here's the screenshot for all architectures -

• For your reference implementation (project using static library). The default settings should work fine -

  

Update 12/03/14Xcode 6 Standard architectures exclude armv7s.

So,armv7s is not needed? Yes. It seems that the general differences between armv7 and armv7s instruction sets are minor. So if you choose not to include armv7s, the targeted armv7 machine code still runs fine on 32 bit A6 devices, and hardly one will notice performance gap.Source

If there is a smarter way for Xcode 6.1+ (iOS 8.1 and above) - please share.

If you are building a universal library and need to support the Simulator (x86_64) then build the framework for all platforms by settingBuild Active Architecture Only toNo.

Many use the build scripts found either here:http://www.raywenderlich.com/41377/creating-a-static-library-in-ios-tutorial or here:https://gist.github.com/sponno/7228256 for their run script in their target.

I was pulling my hair out trying to add x86_64, i386, armv7s, armv7, and arm64 to the Architectures section, only to findlipo -info targetname.a never returning these architectures after a successful build.

In my case, I had to modify the target runscript, specifically step 1 from the gist link, to manually include the architectures using -arch.

Step 1. Build Device and Simulator versionsxcodebuild -target ${PROJECT_NAME} ONLY_ACTIVE_ARCH=NO -configuration ${CONFIGURATION} -sdk iphoneos BUILD_DIR="${BUILD_DIR}"BUILD_ROOT="${BUILD_ROOT}" xcodebuild -target ${PROJECT_NAME} -configuration ${CONFIGURATION} -sdk iphonesimulator -arch x86_64 -arch i386 -arch armv7 -arch armv7s -arch arm64 BUILD_DIR="${BUILD_DIR}" BUILD_ROOT="${BUILD_ROOT}"

Here's a response to your latest question about the difference betweenx86_64 andarm64:

• x86_64 architecture is required for running the 64bit simulator.

• arm64 architecture is required for running the 64bit device (iPhone5s, iPhone 6, iPhone 6 Plus, iPad Air, iPad mini with Retinadisplay).

I run into exactly the same problem and was following this tutorialhttps://github.com/jverkoey/iOS-Framework#faq

The way that I made this work is after putting into the scripts into your Aggregate's Build Phase, before you compile, make sure you compile it using an iphone simulator (I used iPhone6) instead of IOS Device.

which will give me 2 slices: armv7 and x86_64, then drag and drop it into new project is working fine for me.

I uselipo command to combine two built static libraries manually.

EX: I have a static library(libXYZ.a) to build.

I run build forGeneric iOS Device and got Product inDebug-iphoneos/

$ lipo -info Debug-iphoneos/libXYZ.aArchitectures in the fat file: Debug-iphoneos/libXYZ.a are: armv7 arm64

Then I run build for anyiOS Simulator and got Product inDebug-iphonesimulator/

$ lipo -info Debug-iphonesimulator/libXYZ.aArchitectures in the fat file: Debug-iphonesimulator/libXYZ.a are: i386 x86_64

Finally I combine into one to contain all architectures.

$ lipo -create Debug-iphoneos/libXYZ.a Debug-iphonesimulator/libXYZ.a -output libXYZ.a$ lipo -info libXYZ.aArchitectures in the fat file: libXYZ.a are: armv7 i386 x86_64 arm64

My solution was connect my iPhone 6, build on it and I got the project running successfully.

Because I was building for iPhone 6 Simulator.

Setting the build active architectures only to No fixed this problem for me.

Following changes you have to make that's it(change architecture into armv7 and remove others) :-

One other thing to look out for is that XCode is badly handling the library imports, and in many cases the solution is to find the imported file in your project, delete it in Finder or from the command line and add it back again, otherwise it won't get properly updated by XCode. By XCode leaving there the old file you keep running in circles not understanding why it is not compiling, missing the architecture etc.

If you are having this problem in react-native projects with one of the external library. You should remove the project and usereact-native link <package-name> again. That should solve the problem.

I tried using all the above, nothing worked in my case.

I used the SumUp library which was causing this issue.

I fixed it by:

1. Removing the -ObjC parameters (all of them); in previous SumUp libs they required to have the -ObjC populated with parameters to make it work, however the latest version (xc v4.0.1 at the time of my answer here), the docs says remove it.

That still didn't fix the issue, I was still seeing errors all over the place hence coming to this thread,... however, after playing around with the settings the following fixed it:

2. Going into "Build Settings" for your project and then changing "Build Active Architectures Only" to "YES", cleaned, Rebuilt, no errors, Finally!

Set in TARGETS -> MyProject -> User-Defined --> VALID_ARCHS those values: arm64 armv7 x86_64 solved this issue for me.

• ios
• xcode6.1