Pods was rejected as an implicit dependency for 'libPods.a' because its architectures 'x86_64' didn

简介:

引入cocoaPods后。第一次编译,或者运行update后 可能报这个错误:

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

查了些资料,在网上有一种解决方法是去设置podproject的  valid Architectures 与你的项目project的 valid Architectures 一致

试了试没有成功,

经过尝试最后找了解决方式:详细的解决方式例如以下图:

确保3的地方设置为最新的sdk,确保4的地方设置和project设置一样




更新:再次遇到这个问题。依照上面方法无法解决。请尝试下面解决方法:

A friend updated Cocoapods in our project. When I pulled the latest stuff from git I got the following error:

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

This results in

ld: library not found for -lPods-___PODLIBRARY____
clang: error: linker command failed with exit code 1 (use -v to see invocation)

I have searched around for hours now trying to find it. The most common fixes I've tried are..

  • Deleted derived data
  • Delete build data
  • Delete pods, and reinstalled with 'pod install'
  • Clean project
  • All of the above at the same time
  • Experimented with 'Build Active Architecture Only', both in our project and in Pod Project. Inserted armv7 and armv7s as hard code instead of $ variable
  • Experimented with 'Architectures', both in our project and in Pod Project. Inserted armv7 and armv7s as hard code instead of $ variable

We are aiming for iOS 8, iPhones.

My friend got it to work by combining the first 4 options, but I cannot.

Does anyone have any suggestions? We're supposed to release before christmas so production time is precious :D

參考地址:http://stackoverflow.com/questions/27388957/pods-was-rejected-as-an-implicit-dependency-for-libpods-a-because-its-architec






本文转自mfrbuaa博客园博客,原文链接:http://www.cnblogs.com/mfrbuaa/p/5115741.html,如需转载请自行联系原作者

相关文章
|
5月前
|
JavaScript
鬼火起~为什么报错[Vue warn]: Avoid mutating a prop directly since the value will be overwritten whenever the
鬼火起~为什么报错[Vue warn]: Avoid mutating a prop directly since the value will be overwritten whenever the
|
8月前
|
Perl
Pod Performing a deep fetch of the `master` specs repo to improve future perform
Pod Performing a deep fetch of the `master` specs repo to improve future perform
30 0
|
10月前
|
JavaScript
[Vue warn]: Avoid mutating a prop directly since the value will be overwritten whenever the parent .(一)
大致意思就是props接收到的从父组件传过来的tableData不能直接修改。
|
10月前
|
JavaScript
[Vue warn]: Avoid mutating a prop directly since the value will be overwritten whenever the parent .(二)
1.在data中声明一个变量接收props的值,然后再去改变data里的这个值 2. 用computed属性 3.用data保存数据,watch监听
|
11月前
|
Java Maven
An attempt was made to call a method that does not exist. The attempt was made from the following
An attempt was made to call a method that does not exist. The attempt was made from the following
254 0
|
Java 测试技术
出现Error creating bean with name与CONDITIONS EVALUATION REPORT问题
出现Error creating bean with name与CONDITIONS EVALUATION REPORT问题
304 0
出现Error creating bean with name与CONDITIONS EVALUATION REPORT问题
annotationProcessor‘ dependencies won‘t be recognized as kapt annotation processors. Please change
annotationProcessor‘ dependencies won‘t be recognized as kapt annotation processors. Please change
300 0
|
JavaScript
【解决方案】[Vue warn]: Avoid mutating a prop directly since the value will be overwritten whenever the pa
【解决方案】[Vue warn]: Avoid mutating a prop directly since the value will be overwritten whenever the pa
1412 0
E: Unable to correct problems, you have held broken packages.
在使用服务器配置环境中遇到的问题,先将解决方案列下:
When should reread of cl_crm_bol_entity and $scope.$apply be called manually
When should reread of cl_crm_bol_entity and $scope.$apply be called manually
121 0
When should reread of cl_crm_bol_entity and $scope.$apply be called manually