New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
xialin opened this Issue Apr 16, 2014 · 45 comments

Comments

Projects
None yet
@xialin

xialin commented Apr 16, 2014

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

@xialin

This comment has been minimized.

Show comment
Hide comment
@xialin

xialin Apr 16, 2014

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

xialin commented Apr 16, 2014

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

@hassanraza-maavratech

This comment has been minimized.

Show comment
Hide comment
@hassanraza-maavratech

hassanraza-maavratech Jun 24, 2014

Yea it worked thx...

hassanraza-maavratech commented Jun 24, 2014

Yea it worked thx...

@Glavin001

This comment has been minimized.

Show comment
Hide comment
@Glavin001

Glavin001 Aug 12, 2014

Worked for me, too. Thank you!

Glavin001 commented Aug 12, 2014

Worked for me, too. Thank you!

@orta

This comment has been minimized.

Show comment
Hide comment
@orta

orta Aug 12, 2014

Member

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

Member

orta commented Aug 12, 2014

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

@orta orta closed this Aug 12, 2014

@Glavin001

This comment has been minimized.

Show comment
Hide comment
@Glavin001

Glavin001 Aug 12, 2014

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

Glavin001 commented Aug 12, 2014

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

@mhalttu

This comment has been minimized.

Show comment
Hide comment
@mhalttu

mhalttu commented Aug 13, 2014

Agreed.

@hungdm9999

This comment has been minimized.

Show comment
Hide comment
@hungdm9999

hungdm9999 Sep 24, 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 commented Sep 24, 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.

@dmcd

This comment has been minimized.

Show comment
Hide comment
@dmcd

dmcd Oct 24, 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 commented Oct 24, 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

@nonstriater

This comment has been minimized.

Show comment
Hide comment
@nonstriater

nonstriater Dec 16, 2014

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

nonstriater commented Dec 16, 2014

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

@mmiroslav

This comment has been minimized.

Show comment
Hide comment
@mmiroslav

mmiroslav Dec 16, 2014

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

mmiroslav commented Dec 16, 2014

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

@kvasavi

This comment has been minimized.

Show comment
Hide comment
@kvasavi

kvasavi Dec 26, 2014

Thanks!!! the below works for me.

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

kvasavi commented Dec 26, 2014

Thanks!!! the below works for me.

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

@Hackmodford

This comment has been minimized.

Show comment
Hide comment
@Hackmodford

Hackmodford Jan 12, 2015

@kvasavi That did the trick for me too :)

Hackmodford commented Jan 12, 2015

@kvasavi That did the trick for me too :)

@hzb

This comment has been minimized.

Show comment
Hide comment
@hzb

hzb Jan 14, 2015

It doesn't work, the question still remains.

hzb commented Jan 14, 2015

It doesn't work, the question still remains.

@lcmaizld

This comment has been minimized.

Show comment
Hide comment
@lcmaizld

lcmaizld Feb 6, 2015

Thanks!!! it is worked

lcmaizld commented Feb 6, 2015

Thanks!!! it is worked

@KrLx1994roller

This comment has been minimized.

Show comment
Hide comment
@KrLx1994roller

KrLx1994roller Feb 18, 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! 👍

KrLx1994roller commented Feb 18, 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! 👍

@krvc

This comment has been minimized.

Show comment
Hide comment
@krvc

krvc Feb 25, 2015

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 commented Feb 25, 2015

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.

@XQ0820

This comment has been minimized.

Show comment
Hide comment
@XQ0820

XQ0820 Jul 17, 2015

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

XQ0820 commented Jul 17, 2015

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

@ashfurrow

This comment has been minimized.

Show comment
Hide comment
@ashfurrow

ashfurrow Sep 10, 2015

Contributor

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

Contributor

ashfurrow commented Sep 10, 2015

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

@dwdyer

This comment has been minimized.

Show comment
Hide comment
@dwdyer

dwdyer Oct 23, 2015

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 commented Oct 23, 2015

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?

@khanhankkhan

This comment has been minimized.

Show comment
Hide comment
@khanhankkhan

khanhankkhan Oct 24, 2015

why does pods never work in general?

khanhankkhan commented Oct 24, 2015

why does pods never work in general?

@engmsaleh

This comment has been minimized.

Show comment
Hide comment
@engmsaleh

engmsaleh Dec 8, 2015

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

engmsaleh commented Dec 8, 2015

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

@dinuvld

This comment has been minimized.

Show comment
Hide comment
@dinuvld

dinuvld Dec 19, 2015

Indeed, none of them worked for me on Xcode 7.1

dinuvld commented Dec 19, 2015

Indeed, none of them worked for me on Xcode 7.1

@QueenConch

This comment has been minimized.

Show comment
Hide comment
@QueenConch

QueenConch Feb 24, 2016

thanks!It work for me to~@xialin

QueenConch commented Feb 24, 2016

thanks!It work for me to~@xialin

@jkunzelman

This comment has been minimized.

Show comment
Hide comment
@jkunzelman

jkunzelman Apr 7, 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.

jkunzelman commented Apr 7, 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.

@toshiakiokano

This comment has been minimized.

Show comment
Hide comment
@toshiakiokano

toshiakiokano May 20, 2016

Worked for me. Thanks! @xialin

toshiakiokano commented May 20, 2016

Worked for me. Thanks! @xialin

@Ged2323

This comment has been minimized.

Show comment
Hide comment
@Ged2323

Ged2323 May 27, 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 commented May 27, 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.

@HancleLee

This comment has been minimized.

Show comment
Hide comment
@HancleLee

HancleLee May 31, 2016

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

HancleLee commented May 31, 2016

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

@bikisDesign

This comment has been minimized.

Show comment
Hide comment
@bikisDesign

bikisDesign May 31, 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 commented May 31, 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

@Scarafone

This comment has been minimized.

Show comment
Hide comment
@Scarafone

Scarafone Jun 8, 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 commented Jun 8, 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.

@alvincrisuy

This comment has been minimized.

Show comment
Hide comment
@alvincrisuy

alvincrisuy Jun 13, 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 commented Jun 13, 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.

@JoneRen

This comment has been minimized.

Show comment
Hide comment
@JoneRen

JoneRen Jun 15, 2016

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

JoneRen commented Jun 15, 2016

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

@alvincrisuy

This comment has been minimized.

Show comment
Hide comment
@alvincrisuy

alvincrisuy Jun 15, 2016

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

Hope this help.

alvincrisuy commented Jun 15, 2016

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

Hope this help.

@JoneRen

This comment has been minimized.

Show comment
Hide comment
@JoneRen

JoneRen Jun 15, 2016

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

JoneRen commented Jun 15, 2016

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

@mhalttu

This comment has been minimized.

Show comment
Hide comment
@mhalttu

mhalttu Jun 20, 2016

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 commented Jun 20, 2016

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.

@akouzeli

This comment has been minimized.

Show comment
Hide comment
@akouzeli

akouzeli Jul 19, 2016

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 commented Jul 19, 2016

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.

@mlchai

This comment has been minimized.

Show comment
Hide comment
@mlchai

mlchai Jul 19, 2016

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 commented Jul 19, 2016

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
@Zooeee

This comment has been minimized.

Show comment
Hide comment
@Zooeee

Zooeee Aug 8, 2016

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

Zooeee commented Aug 8, 2016

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

@guidmattos

This comment has been minimized.

Show comment
Hide comment
@guidmattos

guidmattos Nov 30, 2016

You saved my life! Thanks!

guidmattos commented Nov 30, 2016

You saved my life! Thanks!

@bhautikappv

This comment has been minimized.

Show comment
Hide comment
@bhautikappv

bhautikappv Dec 13, 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 commented Dec 13, 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.

kiliankoe added a commit to kiliankoe/ParkKit that referenced this issue Jan 4, 2017

fix iOS simulator testing issue
see all the responses here for reference:
CocoaPods/CocoaPods#2053
@benasher44

This comment has been minimized.

Show comment
Hide comment
@benasher44

benasher44 Jan 6, 2017

Member

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!

Member

benasher44 commented Jan 6, 2017

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!

@rtauziac

This comment has been minimized.

Show comment
Hide comment
@rtauziac

rtauziac Sep 25, 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 commented Sep 25, 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.

@luminkhant

This comment has been minimized.

Show comment
Hide comment
@luminkhant

luminkhant Nov 7, 2017

it work for me too.
Thanks @xialin

luminkhant commented Nov 7, 2017

it work for me too.
Thanks @xialin

@JustCallMeDanTheMan

This comment has been minimized.

Show comment
Hide comment
@JustCallMeDanTheMan

JustCallMeDanTheMan Nov 23, 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 (#2053 (comment)) and this fixed the issue for me. Thanks mhalttu!

JustCallMeDanTheMan commented Nov 23, 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 (#2053 (comment)) and this fixed the issue for me. Thanks mhalttu!

@kiraninfogird

This comment has been minimized.

Show comment
Hide comment
@kiraninfogird

kiraninfogird Apr 24, 2018

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

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

kiraninfogird commented Apr 24, 2018

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

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

@Abhishek-NickelFox

This comment has been minimized.

Show comment
Hide comment
@Abhishek-NickelFox

Abhishek-NickelFox commented May 1, 2018

@kiraninfogird : Thanks Alot !!!! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment