Cocoapods: Pods was rejected as an implicit dependency for 'libPods.a' because its architectures '' didn't contain all required architectures 'i386'

Created on 16 Apr 2014 · 47Comments · Source: CocoaPods/CocoaPods

Problem occurred after I updated CocoaPods to latest release last night...

Tried to set Architectures to standard (armv7, armv7s, arm64), set Build Active Architecture Only (Debug) to Yes.

It gave me the following warning/error:
Pods was rejected as an implicit dependency for 'libPods.a' because its architectures '' didn't contain all required architectures 'i386'
Library not found for -lPods

Source

xialin

👍8 ❤4

Most helpful comment

Set Build Active Architectures Only to No in Pods subproject also. It works for me!

mmiroslav on 16 Dec 2014

👍54 ❤4 🎉4 👎3

All 47 comments

deleted pods folder and Podfile.lock and did a pod install and repeated the above setting..
now it's working.

xialin on 16 Apr 2014

👍23

Yea it worked thx...

hassanraza-maavratech on 24 Jun 2014

Worked for me, too. Thank you!

Glavin001 on 12 Aug 2014

Cool, closing as this has just as high visibility on google, but nothing that we need to do. Thanks @xialin

orta on 12 Aug 2014

It would be nice to know _why_ this error arises such that we can _prevent_ instead of solving it.

Glavin001 on 12 Aug 2014

👍3

Agreed.

mhalttu on 13 Aug 2014

my case (Xcode 6), after 'pod install', at Pods project (not Pod targets) settings, Base SDK was set to build with Latest OSX, just change it to Latest iOS SDK then the workspace got compiled fine.

hungdm9999 on 24 Sep 2014

I did the following

Open Xcode 6
Open Preferences
Click the Locations tab
Change the Command Line Tools version to Xcode 6.0
Uninstall cocoapods
$ sudo gem uninstall cocoapods
Uninstall xcodeproj $ sudo gem uninstall xcodeproj
Install xcodeproj
$ sudo gem install xcodeproj
Install cocoapods
$ sudo gem install cocoapods
Run pod --version to verify that it worked

dmcd on 24 Oct 2014

👎1

it doesn't work, (evn:xcode6,cocoapods0.35.0 ) set build active arch only to NO(include debug) worked for me

nonstriater on 16 Dec 2014

Set Build Active Architectures Only to No in Pods subproject also. It works for me!

mmiroslav on 16 Dec 2014

👍54 ❤4 🎉4 👎3

Thanks!!! the below works for me.

Tried to set Architectures to standard (armv7, armv7s, arm64), set Build Active Architecture Only (Debug) to Yes.

kvasavi on 26 Dec 2014

👍8 👎3

@kvasavi That did the trick for me too :)

Hackmodford on 12 Jan 2015

It doesn't work, the question still remains.

hzb on 14 Jan 2015

Thanks!!! it is worked

lcmaizld on 6 Feb 2015

mmiroslav answer is the correct one!

In my case, the project 'Build Active Architectures' was set to 'No'. Correct. But the pods' setting was set to 'Yes'. Changed to 'No' and warking very well! :+1:

KrLx1994roller on 18 Feb 2015

👍6

I am using Xcode 6.1.1. By setting the "Build Active Architectures Only" to No, in main project and Pods subproject helped me to fix the above warning.

krvc on 25 Feb 2015

👍1

I am using Xcode 6.4
Set Build Active Architectures Only to No in Pods subproject also. help me to fix the problem

XQ0820 on 17 Jul 2015

I had this issue when I inadvertently deleted the "Debug" configuration from the Xcode project. Undoing that using git fixed the problem.

ashfurrow on 10 Sep 2015

👍1

I get this problem every time I do a "pod install" (Cocoapods 0.39, Xcode 7 and 7.1).

I get around it by changing the Architectures setting of each pod to $(ARCHS_STANDARD) (by default it gets set to only 32-bit architectures). Shouldn't this issue still be open as I shouldn't need to manually edit files generated by Cocoapods?

dwdyer on 23 Oct 2015

why does pods never work in general?

khanhankkhan on 24 Oct 2015

👍13 👎2 😄1

I have Xcode 7.1 and none of the above worked for me

engmsaleh on 8 Dec 2015

👍5

Indeed, none of them worked for me on Xcode 7.1

dinuvld on 19 Dec 2015

thanks!It work for me to~@xialin

QueenConch on 24 Feb 2016

This seems like an ongoing problem that a number of people have been reporting. I'm experiencing the same and combination of all of the above techniques seems to fix it for a while, but as soon as I install another pod or run pod install everything gets reset and you have to go thru all the trouble shooting steps again. I've tried the prerelease betas and nothing seems to resolve the overall problem. I've followed all the steps in the trouble shooting FAQ. Very frustrating... Sorry to rant but i needed an outlet before I drive myself insane.

SpaceTrucker2196 on 8 Apr 2016

👍4

Worked for me. Thanks! @xialin

toshiakiokano on 20 May 2016

Yeah I had the GoogleMobileAds.framework already in my project. I deleted that then set the Build Active Architecture to 'Yes' then built it then you can set it back to No and it will still build.

Ged2323 on 27 May 2016

none of them work for me!!!Xcode7.3 cocopods1.0.0

HancleLee on 31 May 2016

None of the above worked for me either. Has anyone found a different fix to this issue? Xcode 7.3 cocopods 1.0.0

bikisDesign on 1 Jun 2016

None of the above has worked for me either. I will be trying to uninstall and reinstall, but all these issues first started happening to me when I first updated Cocoapods. Also it seems to build just fine if I am building directly to a physical device or building for simulator iPhone 5s and up. Only iphone 4s and 5 on simulator give me this issue.

Scarafone on 8 Jun 2016

Same here, nothing worked for me. I tried all the steps already. In my case, it is working on iPhone 4s others are not working.

alvincrisuy on 13 Jun 2016

none worked for me too, cocoapod v1.0.1, xcode 7.3, not working on iphone5c, worked on iphone6 and above.

JoneRen on 15 Jun 2016

I solved it by deleting the derived data of my project in /Users/account/Library/Developer/Xcode/DerivedData

Hope this help.

alvincrisuy on 15 Jun 2016

👍7 🎉1 👎1

@alvincrisuy thanks for you quick reply, delete the derived data ,and set the "Build Active Architecture Only " to "YES" worked for me. 👍

JoneRen on 15 Jun 2016

👍8 🎉3 ❤2 👎1

I spent a couple of hours fighting with this, going through all the Google hits I could find. My build worked for the device, but not for the simulator. Here are the steps that finally solved the issue for me:

rm -rf ~/Library/Developer/Xcode/DerivedData/
rm -rf "${HOME}/Library/Caches/CocoaPods"
rm -rf "`pwd`/Pods/"
pod update

And finally going to the Pods project and setting "Build Active Architectures Only" to "No" also for Debug.

mhalttu on 20 Jun 2016

👍8 ❤1 👎1

Thanks a lot @alvincrisuy!
After trying everything related to this issue that I found in Google, I can say your solution was the only one that did the job.

akouzeli on 19 Jul 2016

❤2

For me a combination of things seemed to help.

set platform to 8.0 in Podfile
set "Build Active Architectures Only" to "YES" for BOTH the app and the Pod project files. Setting it to "NO" actually made it not build.
run the commands (mostly deleting the DerivedData folder) in @mhalttu comment

mlchai on 20 Jul 2016

👍4

Using cocoa pod 0.39.0, and 7.3.1, and none of the above solutions help.

Zooeee on 8 Aug 2016

You saved my life! Thanks!

guidmattos on 30 Nov 2016

Hi all,

My project was developed in xcode 6.4 and trying to run it in xcode 8.0 but i got following error.

screeen

please suggest a way to successfully build project.

bhautikappv on 13 Dec 2016

Hi @bhautikappv! Thanks for letting us know! This issue is quite old, so we'd appreciate if you could file a new issue and fill out the issue template. If you could do that, we'd be happy to help. Have a great day!

benasher44 on 6 Jan 2017

I changed the default configuration names from Debug and Release to Dev and Prod before pod install. Don't do this because it breaks everything.
Actually I had to set the new names to the pods and target configuration by hand to solve that, but this is tedious.

rtauziac on 25 Sep 2017

it work for me too.
Thanks @xialin

luminkhant on 7 Nov 2017

I recently hit this issue after incorporating Firebase into a project, before completely configuring it i.e. it still had the default and latest target iOS version. Evidently, when properly configuring it later, sufficiently lowering the iOS target version to something sensible for my needs triggered this warning in Xcode for me. I guess earlier versions of iOS need to support older architectures (e.g. not just arm64), and so adding the need for arm7 later in the life of the project might trigger it... Wild guess, of course.

I'm sure for many, including me, it is my first encounter with Pods, with an entirely "I will do what they tell me to" approach, so a lot of people who have this issue (and find this page through high ranking on Google searches for the warning message contents) may be as utterly clueless as I am. Hence I have joined to post and leave a trail, with my scenario to aid future Google searches, for future fellow clueless folks to follow.

That's a lot of f words, though not as many as I uttered earlier in response to the issue.

Anyway, I followed mhalttu's comments verbatim (https://github.com/CocoaPods/CocoaPods/issues/2053#issuecomment-227248074) and this fixed the issue for me. Thanks mhalttu!

JustCallMeDanTheMan on 23 Nov 2017

👍1

_Deleted pods folder and Podfile.lock and did a pod install and repeated the above setting..._

It's working now...!
Thanks...

kiraninfogird on 24 Apr 2018

👍2 👎1

@kiraninfogird : Thanks Alot !!!! :)

Abhishek-NickelFox on 1 May 2018

Similar problem.
But on test target this doesn't seem to work (worked building and running the project).
Cocoapods 1.5.3 and Xcode 10 (happened after updating xcode)

Nuked the project, reinstalled pods (and the Debug config set to YES).

That worked for me. Thanks all!

wolffan on 19 Sep 2018

I had the same issue recently after migrating to Xcode 10.1.

Building with Debug config was working just fine, however archiving with Release config was generating this warning.
And then archiving would fail, because in the main project all the module imports referring to Pods were failing.

Checking the Build Settings for the Project I realised that iOS Deployment Target was showing a different value for my Release config.
iOS 10.0, while my Podfile was set to platform :ios, '11.0'.