73

When using Podfile for developing iOS 7 app with Xcode5, we always got this issue.

After some searching, seems like no final resolve from CocoaPods ? Maybe resolved at this moment when you see this.

How to resolve such issues right now ?

The issue was: Pods was rejected as an implicit dependency for 'libPods.a' because its architectures 'armv7 armv7s' didn't contain all required architectures 'armv7 armv7s arm64'

Forrest
  • 122,703
  • 20
  • 73
  • 107

4 Answers4

201
  1. Select the Pods project
  2. Change Build Active Architecture Only from Yes to No.

That worked for me.

Note: CocoaPods Troubleshooting Guide recommends matching the Debug setting in your Xcode project, rather than changing the Pod's Build Active Architecture Only. As long as they match it seems to fix the problem.

enter image description here

Amr Lotfy
  • 2,937
  • 5
  • 36
  • 56
funroll
  • 35,925
  • 7
  • 54
  • 59
  • 7
    The guide recommends that you set your project's Build Active Architecture Only from NO to YES for Debug. That will match the CocoaPods setting. I'm guessing that's to make it build faster on Debug builds. I'm not sure why they force it. http://guides.cocoapods.org/using/troubleshooting.html#running-into-build-failures-after-migrating-to-xcode--and-cocoapods- – Paul Solt May 02 '14 at 16:45
  • 5
    Found a nice way to automate this. Just add a [snippet](https://gist.github.com/funroll/7faf18b4972d72cd284e) to the end of your Podfile. – funroll Jun 22 '14 at 04:25
  • 3
    dont mess with the active archiecture on the pods... I ended up getting 30 or so build errors around different pods when I did that. I instead matched my project's debug active architecture to the pods project. – LightningStryk Sep 12 '14 at 20:22
  • I noticed that after I set to Yes, I cleaned and built my project. Then went back and reset it to No and my project still builds correctly. – Kramer Jan 22 '15 at 16:54
  • For those like me new to ios dev and looking for the build settings : https://developer.apple.com/library/ios/recipes/xcode_help-project_editor/Articles/EditingBuildSettings.html – nha Jan 21 '16 at 13:19
26

First, try updating cocoapods in your terminal: gem update cocoapods

If it doesn't work after that, go into your workspace, click on the Pod project, select all Pod targets and set Architectures to (armv7 armv7s arm64).

Still nothing? Try switching it all back to (armv7 armv7s).

xcode screenshot

Alexis C.
  • 4,898
  • 1
  • 31
  • 43
10

I had similar issues on XCode 6.1 wherepod install would frequently re-introduce linking errors. Adding $(OTHER_LDFLAGS) to the my target's "Other Linker Flags" got me through this. Please see if this helps.

danfelabs
  • 1,873
  • 1
  • 18
  • 23
  • You're right man! Thanks a lot for helping. This is the exact error if you're in Xcode 6.1 and you ran pod install! Thanks a lot man. – Salman Hasrat Khan Dec 31 '14 at 10:34
  • Thanks man, that solved my problem too. As a matter of fact `pod install` did warn me about this, but the ignorant that I am ignored it! – M. Porooshani Feb 03 '15 at 09:37
4

Just to chip in to the "possible solutions"-pool and because a lot of people with CocoaPods issues are finding this page from Google:

I tried pretty much all suggested solutions, but the thing that did it for me was: In the Pods project in your workspace, go to Build Settings -> Base-SDK. This should be stated in bold. Press backspace to set it to default and set it back to your preferences again (in my case Latest iOS(iOSx.x)).

This oddly solved all my invalid architecture errors. Might help others.

Elechtron
  • 179
  • 3
  • 6