Xcode 5.1 - No architectures to compile for (ONLY_ACTIVE_ARCH=YES, active arch=x86_64, VALID_ARCHS=i386)

IosXcodexcode5.1

Ios Problem Overview

After updating to Xcode 5.1, I can no longer build my project for the 64-bit simulator, receiving this error:

 No architectures to compile for (ONLY_ACTIVE_ARCH=YES, active arch=x86_64, VALID_ARCHS=i386).

These are my target build settings:

Xcode target build settings

I tried changing "Build Active Architecture" to No, as well as adding "i386" to the "Valid Architectures", unfortunately neither worked. Thanks for any suggestions!

Ios Solutions

Solution 1 - Ios

What you need to do is just set the ONLY_ACTIVE_ARCH to NO (at least works for me). Below is a screenshot for it:

http://imgur.com/e918pG7"><img src="http://i.imgur.com/e918pG7.png" width="700" title="" />

EDIT:

As far as I know (please point it out if there's something wrong, thanks), if you set ONLY_ACTIVE_ARCH to YES, it means the Xcode will only build for the active architecture (which refers to the device that's active in Xcode currently). Seems Xcode's default setting is set Debug to YES, so it won't build binaries for other architectures when you only want to build for a special device that connected to your Mac.

The reason failed to build might be that, the project does not support the architecture of the device you connected. So the best solution is to add the right architecture for your device. Below is a list for architectures & the devices that support:

  • ARMv8/ARM64: iPhone 6, iPhone 5s, iPad Air, Retina iPad Mini
  • ARMv7s: iPhone 5, iPhone 5c, iPad 4
  • ARMv7: iPhone 3GS, iPhone 4, iPhone 4S, iPod 3G/4G/5G, iPad, iPad 2, iPad 3, iPad Mini
  • ARMv6: iPhone, iPhone 3G, iPod 1G/2G

So why "set the ONLY_ACTIVE_ARCH to NO" works? Because the device can still run the binary that built for all architectures you added (pass the build), but will lose some performance. This's just a quick solution, but not best.

Note: The more architectures you added, the bigger the binary will be generated. So it's good to choose right architectures for your project. ;)

Solution 2 - Ios

I had the same error message after upgrading to XCode 5.1. Are you using CocoaPods? If so, this should fix the problem:

  1. Delete the "Pods" project from the workspace in the left pane of Xcode and close Xcode.
  2. Run "pod install" from the command line to recreate the "Pods" project.
  3. Re-open Xcode and make sure "Build Active Architecture Only" is set to "No" in the build settings of both the "Pods" project and your own project.
  4. Clean and build.

Solution 3 - Ios

Add arm64 to the target's valid architectures. Looks like it adds x86-64 architecture to simulator valid architectures as well.

Solution 4 - Ios

If you are using CocoaPods, the most likely problem is because your Pods project Build Settings for Build Active Architecture Only is set to Yes for Debug.

The solution is simple. Change it to No.

Similarly, change to No for your application project.

Solution 5 - Ios

I had similar issue. Got it solved by changing "Architecture" to "$(ARCHS_STANDARD_32_BIT)" in Build Settings for Project.

Now, you have to select Standard architectures (armv7, arm64) - $(ARCHS_STANDARD) since apple recommends apps to be build on 64-bit architecture. Click : Apple document

Solution 6 - Ios

Add: Architectures: $(ARCHS_STANDARD_INCLUDING_64_BIT)

Valid architectures: arm64 armv7 armv7s

Solution 7 - Ios

Just in case, for anyone still encountering the issue despite following the above, check that the simulator you are running is also the supported one. I had mine specified to arm7 and arm7s but was trying to run the app on a 64 bit simulator.

Solution 8 - Ios

To avoid having "pod install" reset only_active_arch for debug each time it's run, you can add the following to your pod file

# Append to your Podfile
post_install do |installer_representation|
    installer_representation.project.targets.each do |target|
        target.build_configurations.each do |config|
            config.build_settings['ONLY_ACTIVE_ARCH'] = 'NO'
        end
    end
end

Solution 9 - Ios

Just add arm64 in valid architecture.i hope it will work for you.

Solution 10 - Ios

My problem was that the Pods project was targeting OS X, despite my Podfile having platform :ios. I'm using cocoapods 0.35.0.rc2.

To fix it, select the Pods project in the project navigator, and check that the Pods PROJECT node (mind you, not the Pods target) is targeting iOS. That is, the architectures build settings should be:

  • Architectures: $(ARCHS_STANDARD)
  • Base SDK: iOS 8.1
  • Supported Platforms: iOS
  • Valid architectures: $(ARCHS_STANDARD)

I also wanted to build all architectures, so I added the following to the Podfile:

post_install do | installer |
    installer.project.build_configurations.each do |config|
        config.build_settings['ONLY_ACTIVE_ARCH'] = 'NO'
    end
end

Solution 11 - Ios

I had to add the following i386 and x86_64 to Valid Architectures. I'm running Xcode 7.2 and targeting iOS 8+. I already had armv7, armv7s and arm64 in there and that was working in Xcode 6.4.

Solution 12 - Ios

I faced the same problem when running my app on iPad using xcode 5.1. It got resolved by removing armv7s from 'valid architectures' and setting the 'build active architectures only' value to No. Both these fields can be found in your app->targets->build settings->architectures.

Solution 13 - Ios

I arrived at this question due to a problem with command line build for simulator in Xcode 7.2. In case anyone else gets here with the same issue, I will share the solution I found:

Apparently there is a bug in Xcode 7.2 that causes xcodebuild to fail when trying to build for simulator. The solution is to specify the option "-destination", e.g:

xcodebuild -project TestBuildCmd.xcodeproj -scheme TestBuildCmd -sdk iphonesimulator -destination 'platform=iOS Simulator,name=iPhone 6' build

Update

The above example command will build a binary including the graphics for iPhone 6 only. If the binary is run on other simulators, the iPhone 6 graphics is scaled to the platform. A better workaround which contains all graphics for all platforms is to specify the parameter PLATFORM_NAME=iphonesimulator, for example:

xcodebuild -project TestBuildCmd.xcodeproj -scheme TestBuildCmd -sdk iphonesimulator -arch i386 PLATFORM_NAME=iphonesimulator build

Solution 14 - Ios

Try removing all previous architectures (i.e. remove the ARCHS_STANDARD setting) at the same time as you add i386 to the Architectures. This should change the active architecture to i386. I encountered a similar issue when I tried to build for armv7 by default, but it kept trying to build for arm64. I changed ARCHS_STANDARD to ARCHS_STANDARD_32_BIT, and this changed the active architecture chosen.

Solution 15 - Ios

In acrhiecture - sometimes to support 6.0 and 7.0 , we exlude arm64

In architectures - > acrchitecture - select standard architecture arm64 armv7 armv7s. Just below in Valid acrchitecture make user arm64 armv7 armv7s is included. This worked for me.

Solution 16 - Ios

I solved this problem using @Kjuly's answer and the specific line:

"The reason failed to build might be that, the project does not support the architecture of the device you connected."

With Xcode loaded it automatically set my iPad app to iPad Air

enter image description here

This caused the dependancy analysis error.

Changing the device type immediately solved the issue:

enter image description here

I don't know why this works but this is a very quick answer which saved me a lot of fiddling around in the background and instantly got the app working to test. I would never have thought that this could be a thing and something so simple would fix it but in this case it did.

Solution 17 - Ios

I found that it was necessary to enter the architecture names by hand:

enter image description here

I don't know why this was necessary, i.e. why these values were not inherited from Xcode itself. But as soon as I did this, the problem went away.

Solution 18 - Ios

In Valid architectures: Select each entry (release, debug) and build and press backspace. It should work

Categories
Recommended Ios Solutions
Recommended Xcode Solutions
Recommended xcode5.1 Solutions

Previous Solution:

What is the difference between os.path.basename() and os.path.dirname()?

Python

Next Solution:

Go naming conventions for const

GoConstantsNaming Conventions

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionebiView Question on Stackoverflow
Solution 1 - IosKjulyView Answer on Stackoverflow
Solution 2 - IosMike OnoratoView Answer on Stackoverflow
Solution 3 - IosxardasView Answer on Stackoverflow
Solution 4 - IossamwizeView Answer on Stackoverflow
Solution 5 - IosJayprakash DubeyView Answer on Stackoverflow
Solution 6 - IosAntonijoDevView Answer on Stackoverflow
Solution 7 - Iosirs8925View Answer on Stackoverflow
Solution 8 - IosJake HallView Answer on Stackoverflow
Solution 9 - IosMuhammad ShauketView Answer on Stackoverflow
Solution 10 - IosJanoView Answer on Stackoverflow
Solution 11 - IostimgcarlsonView Answer on Stackoverflow
Solution 12 - IosAnubhaView Answer on Stackoverflow
Solution 13 - IosJRVView Answer on Stackoverflow
Solution 14 - IoshalifixView Answer on Stackoverflow
Solution 15 - IosAnkish JainView Answer on Stackoverflow
Solution 16 - Iossam_smithView Answer on Stackoverflow
Solution 17 - IosmattView Answer on Stackoverflow
Solution 18 - IosKhaled AnnajarView Answer on Stackoverflow