blocks|key|164510|text|我可以通过更新CocoaPods来解决这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|164511|一、项目清理|164512|164513|在项目导航器中，选择项目|ordered-list-item|164514|选择目标|164515|在生成阶段>使用libPod链接二进制文件中删除所有libPod*.a|offset|length|style|BOLD|164516|164517|II.更新CocoaPods|164518|使用命令pod+install转到|CODE|164519|启动终端并转到您的项目CocoaPods|164520|164521|entityMap^0|0|0|0|0|0|1|Y|0|0|0|E|0|0|H|4|B|0|0|K|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|12|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|13|8|@]|9|@]|A|$]]|$1|H|3|I|5|G|7|14|8|@]|9|@]|A|$]]|$1|J|3|K|5|G|7|15|8|@$L|16|M|17|N|O]]|9|@]|A|$]]|$1|P|3|-4|5|6|7|18|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|19|8|@$L|1A|M|1B|N|O]]|9|@]|A|$]]|$1|S|3|T|5|6|7|1C|8|@$L|1D|M|1E|N|O]|$L|1F|M|1G|N|U]]|9|@]|A|$]]|$1|V|3|W|5|G|7|1H|8|@$L|1I|M|1J|N|O]]|9|@]|A|$]]|$1|X|3|-4|5|6|7|1K|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1L|8|@]|9|@]|A|$]]]|Z|$]]

I was able to fix that by updating CocoaPods.
<h3>I. Project Cleanup</h3>
<ol>
<li>In the project navigator, select your project</li>
<li>Select your target</li>
<li>Remove all libPods*.a in Build Phases &gt; Link Binary With Libraries</li>
</ol>
<h3>II. Update CocoaPods</h3>
<ol>
<li>Launch Terminal and go to your project directory.</li>
<li>Update CocoaPods using the command <code>pod install</code></li>
</ol>

blocks|key|2758312|text|经过多次尝试，我终于解决了这个问题。未设置变量${PODS_ROOT}，我使用下面的技巧。转至Build+Phases+->+Check+Pod+Manifest.lock+->+replace|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2758313|diff+"${PODS_ROOT}/../Podfile.lock"+"${PODS_ROOT}/Manifest.lock"+>+/dev/null|code-block|syntax|javascript|2758314|至|2758315|diff+"${SRCROOT}/Podfile.lock"+"${SRCROOT}/Pods/Manifest.lock"+>+/dev/null|2758316|这对我有帮助。|2758317|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

After many attemps I managed to fix this problem. Variable ${PODS_ROOT} was not set and I do below trick.
Go to Build Phases -> Check Pods Manifest.lock and replace

<pre><code>diff "${PODS_ROOT}/../Podfile.lock" "${PODS_ROOT}/Manifest.lock" &gt; /dev/null
</code></pre>

to 

<pre><code>diff "${SRCROOT}/Podfile.lock" "${SRCROOT}/Pods/Manifest.lock" &gt; /dev/null
</code></pre>

It helps me.

blocks|key|2971111|text|如果您从Podfile中的目标删除所有pods，例如|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2971112|target+'myTarget'+do
pod+'great-stuff',+'~>+4.0'++//+you+deleted+this+last+pod
end|code-block|syntax|javascript|2971113|您需要从Xcode目标构建阶段中手动删除这些构建步骤：|offset|length|style|BOLD|2971114|2971115|Check+Pod+Manifest.lock|unordered-list-item|2971116|Copy+Pod+resources|2971117|2971118|当您运行pod+install时，Cocoapods+(当前稳定版本0.37.2)不会执行此清理。|CODE|2971119|entityMap^0|0|0|B|4|0|0|0|0|0|4|B|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|10|8|@$I|11|J|12|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|13|8|@]|9|@]|A|$]]|$1|N|3|O|5|P|7|14|8|@]|9|@]|A|$]]|$1|Q|3|R|5|P|7|15|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|16|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|17|8|@$I|18|J|19|K|V]]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|X|$]]

If you remove all pods from your target in the Podfile, e.g. 

<pre><code>target 'myTarget' do
pod 'great-stuff', '~&gt; 4.0' // you deleted this last pod
end
</code></pre>

you'll need to manually delete these builds steps from your Xcode target Build Phases: 

<ul>
<li>Check Pods Manifest.lock</li>
<li>Copy Pod resources</li>
</ul>

Cocoapods (current stable version 0.37.2) does not perform this cleanup when you run <code>pod install</code>.

blocks|key|163377|text|如果你的pod是空的|type|unstyled|depth|inlineStyleRanges|entityRanges|data|163378|163379|删除复制pods资源并检查pods清单。|ordered-list-item|163380|从项目|163381|的生成阶段设置中锁定|163382|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|M|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

if your pods are empty 

<ol>
<li>remove copy pods resources and check pods manifest.</li>
<li>lock from build phases settings of your project </li>
</ol>

blocks|key|2758367|text|我在一个错误配置的xcconfig文件中遇到了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2758368|Pods生成的xcconfig没有正确地包含在我使用的自定义xcconfig中。这导致$PODS_ROOT未被设置，导致diff+"/../Podfile.lock"+"/Manifest.lock"失败，原因很明显，Pod错误地将其解释为同步问题。|offset|length|style|CODE|2758369|entityMap^0|0|1O|14|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

I encountered this issue with a misconfigured xcconfig file.

The Pods-generated xcconfig was not correctly #included in the customise xcconfig that I was using. This caused $PODS_ROOT to not be set resulting in the failure of <code>diff "/../Podfile.lock" "/Manifest.lock"</code>, for obvious reasons, which Pods misinterprets as a sync issue.

blocks|key|163409|text|更改目标名称后的|type|unstyled|depth|inlineStyleRanges|entityRanges|data|163410|我的问题是xcconfig使用旧的目标名称。|offset|length|style|BOLD|163411|163412|转到项目文件->+info+->+|unordered-list-item|163413|旧的xcconfig+(调试和发布)|163414|pod+install|163415|163416|它会更新到新的版本。|163417|另外，如果您有丢失的.h文件，这是原因(pods头搜索路径在这些xcconfig中)|163418|entityMap^0|0|0|M|0|0|0|H|0|0|I|0|0|B|0|0|0|A|0|0|16|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@$D|Y|E|Z|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|A|$]]|$1|I|3|J|5|K|7|11|8|@$D|12|E|13|F|G]]|9|@]|A|$]]|$1|L|3|M|5|6|7|14|8|@$D|15|E|16|F|G]]|9|@]|A|$]]|$1|N|3|O|5|K|7|17|8|@$D|18|E|19|F|G]]|9|@]|A|$]]|$1|P|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1B|8|@$D|1C|E|1D|F|G]]|9|@]|A|$]]|$1|S|3|T|5|6|7|1E|8|@$D|1F|E|1G|F|G]]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]]|V|$]]

After changing target name

My problem was xcconfig with old target names.

<ul>
<li>Went to project file -> info -> configuration</li>
<li>Removed old xcconfig (both Debug &amp; Release)</li>
<li>pod install</li>
</ul>

It would update to new ones.

Also if you had missing .h files that's the reason (pods header search path is in these xcconfig)

blocks|key|2758434|text|我的问题是，当我的同事开发人员在项目中添加了一个pod，然后我使用github拉出了项目，然后发生了错误。我运行了pod+install，它用我的开发伙伴添加的新库更新了pod。希望能有所帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2758435|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

My problem was when my fellow developer added a pod in the project and then i pull the project using github then the error occurred. I ran pod install and it updated the pods with new library which was added by my fellow developer. hope it helps.

blocks|key|164664|text|从项目中移除pod并重新安装对我来说很有效。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|164665|有一个很好的GitHub+repository可以从项目中完全移除pods。|offset|length|164666|只需保留PodFile的备份并运行以下命令即可。|164667|164668|gem+install+cocoapods-deintegrate|unordered-list-item|style|BOLD|164669|gem将cocoapods-clean|164670|Go安装到项目目录，然后运行pod+deintegrate|164671|Again+run+pod+clean|164672|Run+pod+install|164673|164674|清理干净后就跑。|164675|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/CocoaPods/cocoapods-deintegrate^0|0|6|H|0|0|0|0|0|X|0|0|J|0|E|F|0|A|9|0|4|B|0|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|17|8|@]|9|@$D|18|E|19|1|1A]]|A|$]]|$1|F|3|G|5|6|7|1B|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|I|3|J|5|K|7|1D|8|@$D|1E|E|1F|L|M]]|9|@]|A|$]]|$1|N|3|O|5|K|7|1G|8|@$D|1H|E|1I|L|M]]|9|@]|A|$]]|$1|P|3|Q|5|K|7|1J|8|@$D|1K|E|1L|L|M]]|9|@]|A|$]]|$1|R|3|S|5|K|7|1M|8|@$D|1N|E|1O|L|M]]|9|@]|A|$]]|$1|T|3|U|5|K|7|1P|8|@$D|1Q|E|1R|L|M]]|9|@]|A|$]]|$1|V|3|-4|5|6|7|1S|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1T|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1U|8|@]|9|@]|A|$]]]|Z|$10|$5|11|12|13|A|$14|15]]]]

Removing pods from the project and re-installing worked for me.

There is nice <a href="https://github.com/CocoaPods/cocoapods-deintegrate" rel="noreferrer">GitHub repository</a> that can completely remove the pods from the project.

Just keep the backup of your PodFile and run below commands.

<ul>
<li>gem install cocoapods-deintegrate</li>
<li>gem install cocoapods-clean</li>
<li>Go to the project directory and run pod deintegrate</li>
<li>Again run pod clean</li>
<li>Run pod install</li>
</ul>

Clean and run.

blocks|key|2758597|text|这让我今天很开心！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2758598|2758599|删除项目中的pod文件folder|ordered-list-item|2758600|Deleting项目文件夹中的pod文件夹|2758601|在项目文件夹中执行pod+install+|2758602|在Xcode|2758603|中执行“清理”操作重建项目|2758604|<代码>G211|2758605|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|S|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|T|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|U|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|V|8|@]|9|@]|A|$]]|$1|J|3|K|5|E|7|W|8|@]|9|@]|A|$]]|$1|L|3|M|5|E|7|X|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|Y|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|Q|$]]

This made my day!

<ol>
<li>Deleting the Podfile.lock file in your project folder</li>
<li>Deleting the Pods folder in your project folder</li>
<li>Execute pod install in your project folder</li>
<li>Do a "Clean" in Xcode</li>
<li>Rebuild your project</li>
</ol>

blocks|key|162350|text|我在最新的ComponentKit+0.14上也遇到了同样的问题。原因是没有设置PODS_ROOT，我发现解决方案是在ComponentKit.xcconfig中添加一行：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|162351|#include+"../Pods/Target+Support+Files/Pods-ComponentKit/Pods-ComponentKit.debug.xcconfig"|code-block|syntax|javascript|162352|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I have the same problem with latest ComponentKit 0.14.
The reason is PODS_ROOT was not set and i have found the solution is add a line to ComponentKit.xcconfig :

<pre><code>#include "../Pods/Target Support Files/Pods-ComponentKit/Pods-ComponentKit.debug.xcconfig"
</code></pre>

blocks|key|163555|text|在我的例子中，在集成WatchKit应用程序后，我得到了同样的错误。为了解决这个问题，我需要在Podfile中添加WatchKit的两个目标：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|163556|target+'MyProject+WatchKit+App'+do
++++platform+:watchos,+'2.0'
++++shared_pods
end

target+'MyProject+WatchKit+App+Extension'+do
++++platform+:watchos,+'2.0'
++++shared_pods
end|code-block|syntax|javascript|163557|PS:也许这发生在我身上，因为我最初错误地为MyProject+WatchKit+App目标安装了pods。|offset|length|style|CODE|163558|entityMap^0|0|0|M|M|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

In my case, I got same error after integrating WatchKit app. To solve problem I needed to add both targets of WatchKit in Podfile:

<pre><code>target 'MyProject WatchKit App' do
 platform :watchos, '2.0'
 shared_pods
end

target 'MyProject WatchKit App Extension' do
 platform :watchos, '2.0'
 shared_pods
end
</code></pre>

PS: Maybe this happened for me because I mistakenly installed pods for <code>MyProject WatchKit App</code> target initially.

blocks|key|162369|text|当你这样做的时候|type|unstyled|depth|inlineStyleRanges|entityRanges|data|162370|pod+install+--verbose|code-block|syntax|javascript|162371|确保：|162372|1-您位于正确的目录中。大多数情况下，当下载github项目时，会有一个主文件夹。在调用pod+install+--verbose之前，您需要在终端中的实际项目名称文件夹(folder文件夹/项目文件夹)中|162373|2-删除旧的pod锁文件夹，然后使用xcode+clean+&+do+pod+install清理项目。|162374|3-让你的rvm保持更新。|162375|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|T|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

When you do 

<pre><code>pod install --verbose
</code></pre>

make sure:

1- you are in the correct directory. Most times, when a github project is downloaded, there will be a master folder. You need to be inside the actual project name folder(masterfolder/project folder) in the terminal before you invoke pod install --verbose

2- Delete the old pod lock folder then clean the project using xcode clean &amp; do pod install.

3- Keep your rvm updated.

blocks|key|2758725|text|在你的项目中检查Pod可能没有被推送到Git。很明显，由于无法找到Pods目录，编译将会中断|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2758726|+diff+"${PODS_ROOT}/../../Podfile.lock"+"${PODS_ROOT}/Manifest.lock"+>+/dev/null|code-block|syntax|javascript|2758727|我通过在导航到我的项目目录后在终端中发出pod+install来解决这个问题。|offset|length|style|CODE|2758728|事实上，我有一个错误的cannot+find+pod+command，这意味着没有安装cocoapods。这是通过gem+install+cocoapods修复的。如果你得到任何依赖错误，只需安装每个报告缺失的命令即可。在我的例子中，我必须更新Ruby，然后cocoapods被正确安装，并且我能够使用命令pod+install。|2758729|PS。如果您有Pods目录，请尝试pod+update。也许你的库需要更新。|2758730|entityMap^0|0|0|K|B|0|B|N|17|9|1L|L|3L|9|49|B|0|H|A|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@$I|V|J|W|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|X|8|@$I|Y|J|Z|K|L]|$I|10|J|11|K|L]|$I|12|J|13|K|L]|$I|14|J|15|K|L]|$I|16|J|17|K|L]]|9|@]|A|$]]|$1|O|3|P|5|6|7|18|8|@$I|19|J|1A|K|L]]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|R|$]]

Check in your project that Pods are maybe not being pushed to Git. So it's obvious that compile will break since it cannot find the Pods directory

<pre><code> diff "${PODS_ROOT}/../../Podfile.lock" "${PODS_ROOT}/Manifest.lock" &gt; /dev/null
</code></pre>

I solved this by issuing <code>pod install</code> in the Terminal after navigating to my project's directory. 

Indeed, I had an error <code>cannot find pod command</code> which meant that <code>cocoapods</code> were not installed. This is fixed via <code>gem install cocoapods</code>. If you get any dependency error, just install each command that is reported missing. In my case I had to update Ruby and after that <code>cocoapods</code> were installed properly and I was able to use the command <code>pod install</code>.

PS. If you have Pods directory, try <code>pod update</code>. Maybe your library needs updating.

blocks|key|2971578|text|对我来说，问题是我通过复制现有的目标，在我的应用程序中创建了一个新的目标，但忘记将目标添加到Podfile中。由于某些原因，克隆的目标确实工作了几天，没有出现问题，但过了一段时间后，它由于这个错误而无法构建。我必须在Podfile中为我的克隆项目目标创建一个新的目标条目，然后运行pod+install。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2971579|entityMap^0|1A|7|3W|B|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

For me the problem was that I made a new target in my app by duplicating an existing one, but forgot to add the target to the <code>Podfile</code>. For some reason, the cloned target did work for days without problems, but after a while it failed to build by this error. I had to create a new target entry for my cloned project target in the Podfile then run <code>pod install</code>.

blocks|key|166348|text|当我尝试删除以前安装的库时，我遇到了这个问题|type|unstyled|depth|inlineStyleRanges|entityRanges|data|166349|@Michal的回答帮助了我|166350|Remove+or+uninstall+library+previously+added+:+cocoapods|offset|length|166351|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/13751147/remove-or-uninstall-library-previously-added-cocoapods^0|0|0|0|1K|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@$F|S|G|T|1|U]]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

i had this issue when i was trying to remove previously installed library

@Michal's answer helped me

<a href="https://stackoverflow.com/questions/13751147/remove-or-uninstall-library-previously-added-cocoapods">Remove or uninstall library previously added : cocoapods</a>

blocks|key|2971617|text|我找到了解决方案:运行：pod+update而不是pod+install。错误已修复！|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2971618|entityMap^0|C|A|P|B|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

I found my solution: Run:<code>pod update</code> instead of <code>pod install</code>. The error was fixed!

blocks|key|2758790|text|我不小心删除了我试图安装pod的文件夹，然后将其解压回去。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2758791|它是这样的:+1)+cd在你的项目文件夹中2)压缩你的项目3)删除项目文件夹4)解压文件夹5)现在即使你有这个文件夹，你也应该从终端再次进入这个文件夹|2758792|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I accidentally removed and then unpack back folder from where I tried to install pod. 
It was like this:
1) cd in your project folder
2) zip your project
3) remove project folder
4) unzip folder back 
5) from now even you have this folder you should go to this folder again from the terminal

blocks|key|163642|text|我的问题是可可豆荚版本，所以我安装了最新的版本：sudo+gem+install+cocoapods+--pre，然后是pod+update|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|163643|这对我很管用|163644|entityMap^0|O|W|1O|A|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|P|8|@]|D|@]|E|$]]]|I|$]]

My problem was the cocoa pods version so I installed the latest with: 
<code>sudo gem install cocoapods --pre</code> 
Then <code>pod update</code>

That worked for me

blocks|key|166405|text|适用于我的步骤(XCode+8.3.3/XCode+9+beta+with+a+Swift+3.1+project)|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|166406|+-+Navigate+to+your+project+directory
+-+pod+install+//which+then+asks+you+to+do+the+next+step
+-+pod+repo+update+//takes+a+while+to+update+the+repo
+-+pod+update
+-+pod+install
+-+Close+Xcode+session
+-+Open+and+Clean+the+project
+-+Build/Run|code-block|syntax|javascript|166407|也就是make+sure+you+open+the+.xcworkspace+file+rather+than+the+project+file+(.xcodeproj)+when+working+with+pods.这应该可以解决链接的任何错误，例如"Apple+Mach+-O+Linker命令失败“|BOLD|166408|entityMap^0|8|1D|0|0|3|2X|3|2X|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|S|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|T|8|@$9|U|A|V|B|M]|$9|W|A|X|B|C]]|D|@]|E|$]]|$1|N|3|-4|5|6|7|Y|8|@]|D|@]|E|$]]]|O|$]]

The steps that worked for me (<code>XCode 8.3.3/XCode 9 beta with a Swift 3.1 project</code>)

<pre><code> - Navigate to your project directory
 - pod install //which then asks you to do the next step
 - pod repo update //takes a while to update the repo
 - pod update
 - pod install
 - Close Xcode session
 - Open and Clean the project
 - Build/Run
</code></pre>

Also <code>make sure you open the .xcworkspace file rather than the project file (.xcodeproj) when working with pods</code>. That should solve any errors with linking such as "Apple Mach -O Linker command failed"

blocks|key|2758847|text|如果您正在申请项目清理的方式，和您的项目仍然错误。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2758848|您可以转到选项卡Build+Phases，然后找到Check+Pods+Manifest.lock并删除该脚本。|CODE|2758849|然后键入命令，删除与该rm+-rf+Pods类似的文件夹Pods|2758850|然后需要使用rm+Podfile.lock命令删除Podfile.lock|2758851|也许，基于某种情况，您可以删除文件your_project_name.xcworkspace|2758852|最后，您需要使用该命令来安装Pod+pod+install+--repo-update。|2758853|希望这个解决方案能带给你。快乐编码:)|2758854|entityMap^0|7|8|0|8|C|P|O|0|B|B|S|4|0|6|F|0|H|T|0|I|P|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|X|8|@$9|Y|A|Z|B|C]|$9|10|A|11|B|H]]|D|@]|E|$]]|$1|I|3|J|5|6|7|12|8|@$9|13|A|14|B|H]|$9|15|A|16|B|H]]|D|@]|E|$]]|$1|K|3|L|5|6|7|17|8|@$9|18|A|19|B|H]]|D|@]|E|$]]|$1|M|3|N|5|6|7|1A|8|@$9|1B|A|1C|B|H]]|D|@]|E|$]]|$1|O|3|P|5|6|7|1D|8|@$9|1E|A|1F|B|H]]|D|@]|E|$]]|$1|Q|3|R|5|6|7|1G|8|@]|D|@]|E|$]]|$1|S|3|-4|5|6|7|1H|8|@]|D|@]|E|$]]]|T|$]]

If you are applying to the way Project Cleanup and your project still error. 

You can go to tab Build Phases and then Find <code>Check Pods Manifest.lock</code> and remove the script.

Then type command to remove folder <code>Pods</code> like that <code>rm -rf Pods</code>

and then you need to remove Podfile.lock by command <code>rm Podfile.lock</code>

Probably, base on a situation you can remove file <code>your_project_name.xcworkspace</code>

Finally, you need the command to install Pod <code>pod install --repo-update</code>.

Hopefully, this solution comes up with you. Happy coding :)

blocks|key|162465|text|如果你从github下载项目或者从其他地方复制，那么依赖库就不存在，就会出现这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|162466|您只需要在终端中cd到project/project_name+directory，使用ls查看是否有Podfile文件。|offset|length|style|CODE|162467|如果存在Podfile，您只需安装依赖项：|162468|pod+install|code-block|syntax|javascript|162469|entityMap^0|0|8|2|B|U|18|2|1F|7|0|4|7|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@$D|S|E|T|F|G]|$D|U|E|V|F|G]|$D|W|E|X|F|G]|$D|Y|E|Z|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|10|8|@$D|11|E|12|F|G]]|9|@]|A|$]]|$1|J|3|K|5|L|7|13|8|@]|9|@]|A|$M|N]]|$1|O|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|P|$]]

If you download the project from github or copy from other place, then the dependencies library do not exists, there will be this issue. 

You just need to <code>cd</code> to the <code>project/project_name directory</code> in terminal , use <code>ls</code> to check whether there is a <code>Podfile</code> file.

if there exists the <code>Podfile</code>, you just need to install the dependencyies:

<pre><code>pod install
</code></pre>

blocks|key|2759001|text|如果您看到如下所示的错误：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2759002|diff:+/../+Podfile.lock+:没有这样的文件或目录diff:+/Manifest.lock:没有这样的文件或目录错误:沙箱与Podfile.lock不同步。运行'pod+install‘或更新您的CocoaPods安装。|2759003|那么你的项目中的Cocoapods就有问题了。有时cocoapods可能会失去同步，您需要重新启动cocoapods。您应该能够通过以下方法解决此错误：|2759004|2759005|删除项目中的Podfile.lock文件|ordered-list-item|2759006|项目文件夹中的pod文件夹|2759007|在项目文件夹中执行'pod+Podfile.lock‘|2759008|在Xcode|2759009|中执行“清理”操作重建项目|2759010|2759011|entityMap^0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|A|$]]|$1|G|3|H|5|I|7|Y|8|@]|9|@]|A|$]]|$1|J|3|K|5|I|7|Z|8|@]|9|@]|A|$]]|$1|L|3|M|5|I|7|10|8|@]|9|@]|A|$]]|$1|N|3|O|5|I|7|11|8|@]|9|@]|A|$]]|$1|P|3|Q|5|I|7|12|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|13|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|T|$]]

If you are seeing an error like the following:

diff: /../Podfile.lock: No such file or directory 
diff: /Manifest.lock: No such file or directory 
error: The sandbox is not in sync with the Podfile.lock. Run 'pod install' or update your CocoaPods installation.

Then there's a problem with Cocoapods in your project. Sometimes cocoapods can get out of sync and you need to re-initiate cocoapods. You should be able to resolve this error by:

<ol>
<li>Deleting the Podfile.lock file in your project folder</li>
<li>Deleting the Pods folder in your project folder</li>
<li>Execute 'pod install' in your project folder</li>
<li>Do a "Clean" in Xcode</li>
<li>Rebuild your project</li>
</ol>

blocks|key|2971986|text|我有一个错误：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2971987|diff:+/../+Podfile.lock+:没有这样的文件或目录diff:+/Manifest.lock:没有这样的文件或目录错误:沙箱与Podfile.lock不同步。|2971988|我第一次从bitbucket拉取请求。我清理了我的项目并尝试了所有方法(+pod安装、pod更新等)。但是上面的答案对我都不起作用。然后，我只需检查我安装pod的路径，并更正它，然后再次安装，它就工作了。确保在.xcodeproj或.xcworkspace(如果已经存在)位置之前提供路径。可能会有人从中受益。|2971989|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I had error:

diff: /../Podfile.lock: No such file or directory diff: /Manifest.lock: No such file or directory error: The sandbox is not in sync with the Podfile.lock. 

I pulled request from bitbucket for first time. I cleaned my project and tried everything(pod install, pod update etc.) but none of the above answer worked for me. Then I just check the path where I was installing the pod and corrected it and installed again,It just worked. Make sure give the path just before where .xcodeproj or .xcworkspace(if it is already there)exist. May be someone get benefitted from this.

blocks|key|164899|text|我也犯了同样的错误。首先，我更新cocoapods|type|unstyled|depth|inlineStyleRanges|entityRanges|data|164900|sudo+gem+install+cocoapods|code-block|syntax|javascript|164901|然后使用Pod+install命令安装Pod对我有效。|164902|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I had same error. First I update cocoapods using

<pre><code>sudo gem install cocoapods
</code></pre>

then install pods using Pod install command worked for me.

blocks|key|2972023|text|您需要在自定义的xcconfig中包含Pods生成的xcconfig路径。对我来说，这是由于xcconfig文件配置错误造成的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2972024|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

You need to include Pods-generated xcconfig path in your customized xcconfig. For me this was due to that misconfigured xcconfig file.

blocks|key|162583|text|请执行以下步骤：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|162584|1:删除项目文件夹中的Podfile.lock文件|162585|2:删除项目文件夹中的Pods文件夹|162586|3:在项目文件夹中执行'pod+install‘|162587|4:在Xcode中做一次“清理”|162588|5:重建你的项目|162589|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

Please do the following steps:

1: Deleting the Podfile.lock file in your project folder

2: Deleting the Pods folder in your project folder

3: Execute 'pod install' in your project folder

4: Do a "Clean" in Xcode

5: Rebuild your project

blocks|key|2759229|text|我使用捆绑包中的可可豆荚安装。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2759230|2759231|安装bundle+exec+pod+install|unordered-list-item|offset|length|style|CODE|2759232|+|2759233|在项目根目录中添加Gemfile+|2759234|
|2759235|在bundler中添加所需的gem，然后始终使用bundle+exec+pod+install|2759236|2759237|如果您不知道这些步骤中的某个步骤的使用方法，在google上搜索会有所帮助:)|2759238|entityMap^0|0|0|2|N|0|0|0|0|O|N|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|X|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|Y|8|@$F|Z|G|10|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|11|8|@]|9|@]|A|$]]|$1|L|3|M|5|E|7|12|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|13|8|@]|9|@]|A|$]]|$1|P|3|Q|5|E|7|14|8|@$F|15|G|16|H|I]]|9|@]|A|$]]|$1|R|3|-4|5|6|7|17|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|18|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|19|8|@]|9|@]|A|$]]]|V|$]]

I use the cocoa pods installation from the bundle.

<ul>
<li>Install bundler</li>
<li>Add Gemfile in root of project</li>
<li>Add required gems in Gemfile</li>
<li><code>bundle install</code></li>
<li>and then always use <code>bundle exec pod install</code></li>
</ul>

If you don't know how-tos of one of these steps, searching on google will help :)

blocks|key|162597|text|pod+deintegrate+<PROJECT>.XCODEPROJ+//+will+deintegrate+cocoapods
pod+install+//+installs+the+pods|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|162598|unstyled|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$B|C]]|$1|D|3|-4|5|E|7|H|8|@]|9|@]|A|$]]]|F|$]]

<pre><code>pod deintegrate &lt;PROJECT&gt;.XCODEPROJ // will deintegrate cocoapods
pod install // installs the pods
</code></pre>

blocks|key|162614|text|我已经搜索了几个小时，我找到了如下解决方案：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|162615|在我的例子中，方法1是可行的。|162616|方法1:|offset|length|style|BOLD|162617|162618|选择目标>转到生成阶段>单击将二进制文件与库链接>删除所有libPods.a文件|ordered-list-item|162619|<代码>G211|162620|162621|打开终端>直接进入您的项目>运行：|162622|162623|pod安装|162624|162625|清理并生成项目|162626|162627|ref.1|162628|方法2:|162629|162630|162631|162632|pod+deintegrate+--详细pod安装--详细|162633|ref.2|162634|方法3:|162635|162636|选择目标>转到构建设置>单击"%2B“sign|162637|162638|162639|添加2个用户定义的设置:左侧=右侧|162640|162641|PODS_ROOT+=+${SRCROOT}/Pods|162642|和|162643|++++PODS_PODFILE_DIR_PATH+=+${SRCROOT}/|code-block|syntax|javascript|162644|ref.3|162645|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/31738557/10717246|1|https://stackoverflow.com/a/35446801/10717246|2|https://stackoverflow.com/a/47107769/10717246^0|0|0|0|4|0|0|7|4|E|A|T|9|0|0|0|0|0|0|0|0|0|0|5|0|0|0|4|0|0|0|0|0|0|5|1|0|0|4|0|0|7|4|0|0|0|0|0|0|0|0|0|5|2|0^^$0|@$1|2|3|4|5|6|7|27|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|28|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|29|8|@$F|2A|G|2B|H|I]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|2C|8|@]|9|@]|A|$]]|$1|K|3|L|5|M|7|2D|8|@$F|2E|G|2F|H|I]|$F|2G|G|2H|H|I]|$F|2I|G|2J|H|I]]|9|@]|A|$]]|$1|N|3|O|5|6|7|2K|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|2L|8|@]|9|@]|A|$]]|$1|Q|3|R|5|M|7|2M|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|2N|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|2O|8|@]|9|@]|A|$]]|$1|V|3|-4|5|6|7|2P|8|@]|9|@]|A|$]]|$1|W|3|X|5|M|7|2Q|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|2R|8|@]|9|@]|A|$]]|$1|Z|3|10|5|6|7|2S|8|@]|9|@$F|2T|G|2U|1|2V]]|A|$]]|$1|11|3|12|5|6|7|2W|8|@$F|2X|G|2Y|H|I]]|9|@]|A|$]]|$1|13|3|-4|5|6|7|2Z|8|@]|9|@]|A|$]]|$1|14|3|R|5|M|7|30|8|@]|9|@]|A|$]]|$1|15|3|-4|5|6|7|31|8|@]|9|@]|A|$]]|$1|16|3|17|5|6|7|32|8|@]|9|@]|A|$]]|$1|18|3|19|5|6|7|33|8|@]|9|@$F|34|G|35|1|36]]|A|$]]|$1|1A|3|1B|5|6|7|37|8|@$F|38|G|39|H|I]]|9|@]|A|$]]|$1|1C|3|-4|5|6|7|3A|8|@]|9|@]|A|$]]|$1|1D|3|1E|5|M|7|3B|8|@$F|3C|G|3D|H|I]]|9|@]|A|$]]|$1|1F|3|-4|5|6|7|3E|8|@]|9|@]|A|$]]|$1|1G|3|-4|5|6|7|3F|8|@]|9|@]|A|$]]|$1|1H|3|1I|5|M|7|3G|8|@]|9|@]|A|$]]|$1|1J|3|-4|5|6|7|3H|8|@]|9|@]|A|$]]|$1|1K|3|1L|5|6|7|3I|8|@]|9|@]|A|$]]|$1|1M|3|1N|5|6|7|3J|8|@]|9|@]|A|$]]|$1|1O|3|1P|5|1Q|7|3K|8|@]|9|@]|A|$1R|1S]]|$1|1T|3|1U|5|6|7|3L|8|@]|9|@$F|3M|G|3N|1|3O]]|A|$]]|$1|1V|3|-4|5|6|7|3P|8|@]|9|@]|A|$]]]|1W|$1X|$5|1Y|1Z|20|A|$21|22]]|23|$5|1Y|1Z|20|A|$21|24]]|25|$5|1Y|1Z|20|A|$21|26]]]]

I had been searching for hours and I found solutions as follow:
In my case, method 1 works.
Method 1:
<ol>
<li>choose the target &gt; go to Build Phases &gt; click Link Binary With Libraries &gt; remove all libPods.a files
</li>
<li>open Terminal &gt; direct to your project &gt; run:
<pre><code> pod install
</code></pre>
</li>
<li>clean and build project
</li>
</ol>
<a href="https://stackoverflow.com/a/31738557/10717246">ref.1</a>
Method 2:
<ol>
<li>open Terminal &gt; direct to your project &gt; run:
<pre><code> pod deintegrate --verbose 
 pod install --verbose
</code></pre>
</li>
</ol>
<a href="https://stackoverflow.com/a/35446801/10717246">ref.2</a>
Method 3:
<ol>
<li>choose the target &gt; go to Build Settings &gt; click &quot;+&quot; sign
</li>
<li>add 2 User-Defined Settings: [to the left = to the right]
<pre><code> PODS_ROOT = ${SRCROOT}/Pods
</code></pre>
</li>
</ol>
and
<pre><code> PODS_PODFILE_DIR_PATH = ${SRCROOT}/
</code></pre>
<a href="https://stackoverflow.com/a/47107769/10717246">ref.3</a>

blocks|key|2972149|text|我试了所有的方法，但问题仍然存在。在那之后，我这样做了，它工作得很快(尽可能地流畅)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2972150|2972151|打开.xcworkspace文件。|ordered-list-item|2972152|如果在Xcode10上使用Cordova，则更改为传统构建系统。|2972153|转到Podfile的目标/项目。选择Deployment+traget+as+11%2B|2972154|，然后将debug和release更改为Pods.build/release。它是附加在我的case.Pic中的App.debug/release。希望能有所帮助。|2972155|2972156|📷|atomic|offset|length|2972157|​|2972158|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/c2b45a15a7c3c0747c9c9b6e67741b2b.png|imageAlt^0|0|0|0|0|0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|13|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|14|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|15|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|16|8|@]|9|@]|A|$]]|$1|J|3|K|5|E|7|17|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|18|8|@]|9|@]|A|$]]|$1|M|3|N|5|O|7|19|8|@]|9|@$P|1A|Q|1B|1|1C]]|A|$]]|$1|R|3|S|5|6|7|1D|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]]|U|$V|$5|W|X|Y|A|$Z|10|11|-4]]]]

I tried everything, but the problem persisted.
After that I did this and it worked ASAP (As Smooth As Possible).

<ol>
<li>Open the .xcworkspace file. </li>
<li>Change to legacy build system if using Cordova on Xcode 10.</li>
<li>Go to target/project of Podfile. Select Deployment traget as 11+</li>
<li>Then Change the debug and release to Pods-.build/release. It was App.debug/release in my case.Pic attached. Hope it helps.
<a href="https://i.stack.imgur.com/QLl9o.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/QLl9o.png" alt="CHange the Debug Release in Pod"></a></li>
</ol>

blocks|key|2759370|text|对于我来说，在flutter中工作，由于现有的配置，配置不是自动添加的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2759371|向Flutter/Release.xcconfig和Flutter/Debug.xcconfig添加#include+"Pods/Target+Support+Files/Pods-Runner/Pods-Runner.profile.xcconfig"|offset|length|style|CODE|2759372|解决了问题。|2759373|entityMap^0|0|1|O|Q|M|1E|25|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]|$D|P|E|Q|F|G]|$D|R|E|S|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|T|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|K|$]]

For me, working in flutter, the configuration was not automatically added due the existing configuration.

Adding <code>#include "Pods/Target Support Files/Pods-Runner/Pods-Runner.profile.xcconfig"</code> to <code>Flutter/Release.xcconfig</code> and <code>Flutter/Debug.xcconfig</code> 

solved the issue.

blocks|key|166678|text|我遇到了同样的问题，我将所有内容都更新到了的最新版本，地址是:+npm+-v+6.4.1++-v+v10.2.1+pod+--version+1.5.3|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|166679|致:+npm+-v+6.5.0节点-v+v11.8.0+pod+--版本1.6.0|166680|并修复它|166681|entityMap^0|L|O|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|P|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|K|$]]

I had the same issue
I update everything to the latest
from: 
npm -v 6.4.1 
node -v v10.2.1
pod --version 1.5.3

to:
npm -v 6.5.0 
node -v v11.8.0
pod --version 1.6.0

and fix it

blocks|key|166694|text|我的工作答案是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|166695|166696|Install使用以下命令更新您的cocoapods+:+pod+update+|ordered-list-item|166697|使用此命令安装新的pod。pod+install+|166698|最后一条命令:+sudo+gem+install+cocoapods。|166699|166700|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|N|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|O|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|P|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|Q|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|L|$]]

My working answer is:

<ol>
<li>Install update your cocoapods by this command:
pod update</li>
<li>Install your new pods by this command.
pod install</li>
<li>Last one command:
sudo gem install cocoapods.</li>
</ol>

blocks|key|2972198|text|运行这个，你的错误就会消失。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2972199|rm+-rf+Pods+&&+gem+install+cocoapods+&&+pod+install|offset|length|style|CODE|2972200|entityMap^0|0|0|1F|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Run this, and your errors will vanish

<code>rm -rf Pods &amp;&amp; gem install cocoapods &amp;&amp; pod install</code>

blocks|key|163935|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|163936|转到构建阶段->+Check+Pod+Manifest.lock+|unordered-list-item|offset|length|style|BOLD|163937|Replace+|163938|163939|${PODS_ROOT}/Manifest.lock|code-block|syntax|javascript|163940|通过以下方式：|163941|${SRCROOT}/Podfile.lock"+"${SRCROOT}/Pods/Manifest.lock|163942|签入图像：|163943|​|163944|📷|atomic|163945|163946|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/8d1d9b47c4189cf1986e634e3d6678c8.png|imageAlt^0|0|2|U|0|0|0|0|0|0|0|0|0|1|0|0|0^^$0|@$1|2|3|-4|4|5|6|1A|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|1B|7|@$D|1C|E|1D|F|G]]|8|@]|9|$]]|$1|H|3|I|4|C|6|1E|7|@]|8|@]|9|$]]|$1|J|3|-4|4|5|6|1F|7|@]|8|@]|9|$]]|$1|K|3|L|4|M|6|1G|7|@]|8|@]|9|$N|O]]|$1|P|3|Q|4|5|6|1H|7|@]|8|@]|9|$]]|$1|R|3|S|4|M|6|1I|7|@]|8|@]|9|$N|O]]|$1|T|3|U|4|5|6|1J|7|@]|8|@]|9|$]]|$1|V|3|W|4|5|6|1K|7|@]|8|@]|9|$]]|$1|X|3|Y|4|Z|6|1L|7|@]|8|@$D|1M|E|1N|1|1O]]|9|$]]|$1|10|3|W|4|5|6|1P|7|@]|8|@]|9|$]]|$1|11|3|-4|4|5|6|1Q|7|@]|8|@]|9|$]]]|12|$13|$4|14|15|16|9|$17|18|19|-4]]]]

<ul>
<li>Go to Build Phases -> Check Pods Manifest.lock </li>
<li>Replace </li>
</ul>

<pre><code>${PODS_ROOT}/Manifest.lock
</code></pre>

with:

<pre><code>${SRCROOT}/Podfile.lock" "${SRCROOT}/Pods/Manifest.lock
</code></pre>

Check in image :

<a href="https://i.stack.imgur.com/wpLfB.png" rel="noreferrer"><img src="https://i.stack.imgur.com/wpLfB.png" alt="enter image description here"></a>

blocks|key|2972281|text|我在一个Flutter项目中遇到了这个问题。我刚刚在xCode中打开了iOS模块，Build+Clean文件夹为我工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2972282|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I faced this problem in a Flutter project. I just opened iOS Module in xCode and Build Clean Folder worked for me.

blocks|key|162769|text|尝试在Podfile中设置正确的目标，然后运行pod+update或pod+install|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|162770|​|162771|📷|atomic|162772|162773|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/e36762df1b433b7acf801fc30b09294b.png|imageAlt^0|3|7|N|A|Y|B|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]|$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|11|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|12|8|@]|D|@$9|13|A|14|1|15]]|E|$]]|$1|K|3|G|5|6|7|16|8|@]|D|@]|E|$]]|$1|L|3|-4|5|6|7|17|8|@]|D|@]|E|$]]]|M|$N|$5|O|P|Q|E|$R|S|T|-4]]]]

Try to set up the correct target in <code>Podfile</code> and then run <code>pod update</code> or <code>pod install</code>

<a href="https://i.stack.imgur.com/0xWzA.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/0xWzA.png" alt="ios platform target"></a>

blocks|key|2972347|text|我在Ionic-3上也遇到了同样的问题，我做了上述的一些步骤，但它们都不适用于我。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2972348|对于Ionic，删除ios平台|2972349|$+ionic+cordova+platform+remove+ios
$+ionic+cordova+platform+add+ios|code-block|syntax|javascript|2972350|打开xcode，然后尝试构建。这对我很有效:-)|2972351|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|O|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

I had the same issue with Ionic-3, I did some above mention steps but none of them worked for me.

For Ionic
Remove the ios platform

<pre><code>$ ionic cordova platform remove ios
$ ionic cordova platform add ios
</code></pre>

Open xcode then try to build.
this worked for me :-)

blocks|key|2972380|text|从这些答案中，我完全没有得到任何结果。必须通过运行cordova+platform+add+ios重新创建项目。我已经注意到，即使是新生成的项目(在我的例子中)+Firebase+pod也会一次又一次地导致错误消息。在我看来，Xcode或CocoaPods中的一些(Firebase，RestKit)+pod看起来像是一个bug。要包含pod，我可以简单地编辑我的config.xml并运行cordova+platform+add+iOS，它会自动为我做所有的事情。不过，我不确定它是否在所有情况下都能工作。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2972381|编辑：我有一个来自以前iOS/Xcode的Podfile，但今天最新的Podfile中有#+DO+NOT+MODIFY+--+auto-generated+by+Apache+Cordova。这打开了我脑海中的一盏灯，尝试这种方法。看起来有点微不足道，但工作和我的Firebase功能工作。|BOLD|2972382|entityMap^0|P|O|35|5|3B|9|52|A|5F|O|0|0|3|B|3|F|5|L|7|Z|7|18|1F|3O|8|0^^$0|@$1|2|3|4|5|6|7|K|8|@$9|L|A|M|B|C]|$9|N|A|O|B|C]|$9|P|A|Q|B|C]|$9|R|A|S|B|C]|$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|V|8|@$9|W|A|X|B|H]|$9|Y|A|Z|B|C]|$9|10|A|11|B|C]|$9|12|A|13|B|C]|$9|14|A|15|B|C]|$9|16|A|17|B|C]|$9|18|A|19|B|C]]|D|@]|E|$]]|$1|I|3|-4|5|6|7|1A|8|@]|D|@]|E|$]]]|J|$]]

Completely nothing worked out for me from these answers. Had to create the project again by running <code>cordova platform add ios</code>. What I've noticed, even freshly generated project with (in my case) Firebase pods caused the error message over and over again. In my opinion looks like a bug for some (Firebase, RestKit) pods in <code>Xcode</code> or <code>CocoaPods</code>. To have the pods included I could simply edit my <code>config.xml</code> and run <code>cordova platform add iOS</code>, which did everything for me automatically. Not sure if it will work in all scenarios though.

Edit: I had a <code>Podfile</code> from previous <code>iOS</code>/<code>Xcode</code>, but the newest as of today have <code># DO NOT MODIFY -- auto-generated by Apache Cordova</code> in the <code>Podfile</code>. This turned on a light in my head to try the approach. Looks a bit trivial, but works and my <code>Firebase</code> features worked out.

blocks|key|162863|text|通过安装cordova版本9修复了ionic应用程序的问题，尝试了上面所有的解决方案，大多数都是通过xcode链接的，但在我的ionic应用程序上都不起作用|type|unstyled|depth|inlineStyleRanges|entityRanges|data|162864|如果任何人在他们的cordova应用程序上遇到同样的问题，请更新到cordova+9来解决这个问题|162865|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Fixed my issue with ionic app by installing cordova version 9, tried all above solution mostly linked with xcode neither worked for my ionic app

If anyone facing same issue with their cordova app kindly update to cordova 9 to fix this

blocks|key|164066|text|当我添加一个新的开发者帐号时，我得到了这个错误。我更改了项目名称下的Team，但我错过了在Pods文件夹下更新它。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|164067|当我在Pods->+Signing+->+Team下的Teams选项下更新了新的开发人员ID后，我解决了这个问题，错误消失了，构建成功了。|164068|entityMap^0|Y|4|19|4|0|3|M|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|R|8|@]|D|@]|E|$]]]|I|$]]

I got this error when I added a new developer account. I changed the <code>Team</code> under project name but I missed to update it under the <code>Pods</code> folder.
I solved it once I updated the new developer ID under the Teams option available under <code>Pods-&gt; Signing -&gt; Team</code>, the error was gone and the build succeeded.

blocks|key|2759838|text|我混淆了上面的一些评论，这解决了我的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2759839|I.项目清理|offset|length|style|BOLD|2759840|select+in+>在项目导航器中，选择您的项目|2759841|选择目标|unordered-list-item|2759842|
|2759843|Remove+libPods*.a+in|CODE|2759844|ordered-list-item|2759845|2759846|2759847|II.清理构建文件夹|2759848|在XCode中：Menu+Bar+→+Product+→+Product+->+Clean+build+Folder|2759849|III.更新cocapods|2759850|运行pod+update|2759851|entityMap^0|0|0|6|0|0|0|0|7|A|0|0|0|0|0|A|0|8|1E|0|0|E|0|2|A|0^^$0|@$1|2|3|4|5|6|7|15|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|16|8|@$D|17|E|18|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|19|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|1A|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|1B|8|@]|9|@]|A|$]]|$1|O|3|P|5|L|7|1C|8|@$D|1D|E|1E|F|Q]]|9|@]|A|$]]|$1|R|3|-4|5|S|7|1F|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|1I|8|@$D|1J|E|1K|F|G]]|9|@]|A|$]]|$1|X|3|Y|5|6|7|1L|8|@$D|1M|E|1N|F|Q]]|9|@]|A|$]]|$1|Z|3|10|5|6|7|1O|8|@$D|1P|E|1Q|F|G]]|9|@]|A|$]]|$1|11|3|12|5|6|7|1R|8|@$D|1S|E|1T|F|Q]]|9|@]|A|$]]|$1|13|3|-4|5|6|7|1U|8|@]|9|@]|A|$]]]|14|$]]

I mixed up some comments above and that resolved my problem
I. Project Cleanup
<ol>
<li>In the project navigator, select your project</li>
<li>Select your target</li>
<li>Remove all <code>libPods*.a</code> in <code>Build Phases &gt; Link Binary With Libraries</code></li>
</ol>
II. Clean build folder
In XCode: <code>Menu Bar → Product → Product -&gt; Clean build Folder</code>
III. Update cocapods
Run <code>pod update</code>

blocks|key|164102|text|首先，您必须了解Podfile.lock是什么，然后了解Manifest.lock是什么以及它在哪里使用。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|164103|Podfile保存您拥有的每个依赖项的(optimistic或exact)版本。锁文件只保存确切的版本。|164104|执行pod+install操作后，所有pod都将下载/安装到/pods目录中。您可能想要提交它们，也可能不想。这取决于你的团队。你的团队不能决定他们是否应该提交Podfile.lock。这需要提交，这样团队中的每个开发人员都可以确保他们拥有完全相同的版本。|164105|假设你下载了你团队的代码。，，|164106|，|unordered-list-item|164107|。在项目的根目录中，您只有committed.|164108|Then和Podfile，而Podfile.lock目录不是Pods目录，您可以执行pod+install命令来创建Pods目录。您的每个pod版本的快照应该与来自Podfile.lock.|164109|CocoaPods的所有pod的版本相匹配，并进行了安全检查，以确保与|164110|的版本匹配|164111|这就是Manifest.lock发挥作用的地方。Manifest.lock是您的本地机器创建的锁。它必须与存储库中的最后一次提交(导致pods的更改)生成的Podfile.lock相匹配。如果它不匹配，那么一定有什么东西搞砸了。|164112|有关Manifest.lock文件是什么的文档：|164113|++#+++++Manifest.lock:+A+file+contained+in+the+Pods+folder+that+keeps+track+of
++#+++++the+pods+installed+in+the+local+machine.+This+files+is+used+once+the
++#+++++exact+versions+of+the+Pods+has+been+computed+to+detect+if+that+version
++#+++++is+already+installed.+This+file+is+not+intended+to+be+kept+under+source
++#+++++control+and+is+a+copy+of+the+Podfile.lock.|code-block|syntax|javascript|164114|老实说，我只能想到一种情况，在这种情况下Manifest.lock和Podfile.lock会不同步：|164115|我的意思是，如果你从主分支拉取，那么你会得到主分支的Podfile和锁文件。如果您随后更改了Podfile，然后运行pod+install，那么您将更新Podfile.lock和Manifest.lock，并使它们保持同步。这没有问题。|164116|这是不是仅仅是为了：|164117|你和你的团队没有在你的Podfile或Podfile.lock中提交|164118|+/Pods+merge+conflicts，但他们并没有意识到这一点。或者您没有同时提交Podfile.lock|ordered-list-item|BOLD|164119|Then和successfully.|164120|However，因为Xcode不处理Podfile和Podfile.lock，那么如果您检查目标的构建阶段，您的项目自然可以构建|164121|，您将看到以下|164122|​|164123|📷|atomic|164124|164125|该脚本已记录在here中|164126|#+++++Adds+a+shell+script+build+phase+responsible+for+checking+if+the+Pods
#+++++locked+in+the+Pods/Manifest.lock+file+are+in+sync+with+the+Pods+defined
#+++++in+the+Podfile.lock.
#+++++
#+++++@note+++The+build+phase+is+appended+to+the+front+because+to+fail+fast.
#+++++
#+++++@return+[void]|164127|这些行的作用是:执行diff并确保您的Manifest.lock+(即所有已安装pod版本的本地快照)等于Podfile.lock+(即您的存储库中所有已安装pod版本的当前快照)。|164128|修复可能非常简单，只要确保你的Podfile是你想要的。然后运行pod+install。您还以某种方式意外地更改了/Pods目录中的Manifest.lock+(或者如前所述，可能只提交了锁文件，而没有提交Podfile，反之亦然)。删除/Pods目录不会造成任何危害。之后再做一次pod+install。除非你愿意，否则不要做pod+update。|164129|只需确保您永远不会删除Podfile.lock，否则如果您执行pod+install，则它会将所有依赖项更新为它可以删除的最新版本。|164130|164131|查看和这个关于锁文件的video也很有帮助，CocoaPods+docs关于如何将锁文件用于pod+install和pod+update的不同使用方式，最后看看如何在更详细的this+artsy+blog+on+checksums中使用所有这些逻辑。值得注意的是，单个空格将创建新的校验和，并可能使事物不同步。|164132|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/20213751/what-is-the-usage-of-in-cocoapods|1|https://github.com/CocoaPods/CocoaPods/blob/master/lib/cocoapods/installer.rb#L21-L25|2|IMAGE|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/612cea6922ab4656d5c9d2c255fc146c.png|imageAlt|3|https://github.com/CocoaPods/CocoaPods/blob/master/lib/cocoapods/installer/user_project_integrator/target_integrator.rb#L587-L594|4|https://www.youtube.com/watch?v=H-zK1mEwTe0|5|https://guides.cocoapods.org/using/pod-install-vs-update.html|6|https://artsy.github.io/blog/2016/05/03/podspec-checksums/^0|8|C|S|D|0|0|7|K|A|0|0|2|B|U|5|28|C|0|0|0|0|5|7|E|C|U|4|16|B|1M|4|0|0|0|3|D|O|D|26|C|0|2|D|1|0|0|K|D|Y|C|0|Q|7|1A|7|1M|B|24|C|2H|D|0|0|B|7|J|C|0|1|5|19|C|7|F|0|0|0|7|I|7|Q|C|0|0|0|0|1|2|0|0|7|4|3|0|0|A|4|J|D|1H|C|0|F|7|W|B|1L|5|1U|D|2V|7|3B|5|3X|B|4K|A|0|B|C|V|B|0|0|B|5|4|M|E|5|2F|S|6|0^^$0|@$1|2|3|4|5|6|7|2U|8|@$9|2V|A|2W|B|C]|$9|2X|A|2Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|2Z|8|@$9|30|A|31|B|C]]|D|@$9|32|A|33|1|34]]|E|$]]|$1|H|3|I|5|6|7|35|8|@$9|36|A|37|B|C]|$9|38|A|39|B|C]|$9|3A|A|3B|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|3C|8|@]|D|@]|E|$]]|$1|L|3|M|5|N|7|3D|8|@]|D|@]|E|$]]|$1|O|3|P|5|N|7|3E|8|@]|D|@]|E|$]]|$1|Q|3|R|5|N|7|3F|8|@$9|3G|A|3H|B|C]|$9|3I|A|3J|B|C]|$9|3K|A|3L|B|C]|$9|3M|A|3N|B|C]|$9|3O|A|3P|B|C]]|D|@]|E|$]]|$1|S|3|T|5|N|7|3Q|8|@]|D|@]|E|$]]|$1|U|3|V|5|6|7|3R|8|@]|D|@]|E|$]]|$1|W|3|X|5|6|7|3S|8|@$9|3T|A|3U|B|C]|$9|3V|A|3W|B|C]|$9|3X|A|3Y|B|C]]|D|@]|E|$]]|$1|Y|3|Z|5|6|7|3Z|8|@]|D|@$9|40|A|41|1|42]]|E|$]]|$1|10|3|11|5|12|7|43|8|@]|D|@]|E|$13|14]]|$1|15|3|16|5|6|7|44|8|@$9|45|A|46|B|C]|$9|47|A|48|B|C]]|D|@]|E|$]]|$1|17|3|18|5|6|7|49|8|@$9|4A|A|4B|B|C]|$9|4C|A|4D|B|C]|$9|4E|A|4F|B|C]|$9|4G|A|4H|B|C]|$9|4I|A|4J|B|C]]|D|@]|E|$]]|$1|19|3|1A|5|6|7|4K|8|@]|D|@]|E|$]]|$1|1B|3|1C|5|6|7|4L|8|@$9|4M|A|4N|B|C]|$9|4O|A|4P|B|C]]|D|@]|E|$]]|$1|1D|3|1E|5|1F|7|4Q|8|@$9|4R|A|4S|B|C]|$9|4T|A|4U|B|C]|$9|4V|A|4W|B|1G]]|D|@]|E|$]]|$1|1H|3|1I|5|1F|7|4X|8|@]|D|@]|E|$]]|$1|1J|3|1K|5|1F|7|4Y|8|@$9|4Z|A|50|B|1G]|$9|51|A|52|B|C]|$9|53|A|54|B|C]]|D|@]|E|$]]|$1|1L|3|1M|5|6|7|55|8|@]|D|@]|E|$]]|$1|1N|3|1O|5|6|7|56|8|@]|D|@]|E|$]]|$1|1P|3|1Q|5|1R|7|57|8|@]|D|@$9|58|A|59|1|5A]]|E|$]]|$1|1S|3|1O|5|6|7|5B|8|@]|D|@]|E|$]]|$1|1T|3|1U|5|6|7|5C|8|@]|D|@$9|5D|A|5E|1|5F]]|E|$]]|$1|1V|3|1W|5|12|7|5G|8|@]|D|@]|E|$13|14]]|$1|1X|3|1Y|5|6|7|5H|8|@$9|5I|A|5J|B|C]|$9|5K|A|5L|B|C]|$9|5M|A|5N|B|C]]|D|@]|E|$]]|$1|1Z|3|20|5|6|7|5O|8|@$9|5P|A|5Q|B|C]|$9|5R|A|5S|B|C]|$9|5T|A|5U|B|C]|$9|5V|A|5W|B|C]|$9|5X|A|5Y|B|C]|$9|5Z|A|60|B|C]|$9|61|A|62|B|C]|$9|63|A|64|B|C]]|D|@]|E|$]]|$1|21|3|22|5|6|7|65|8|@$9|66|A|67|B|C]|$9|68|A|69|B|C]]|D|@]|E|$]]|$1|23|3|-4|5|6|7|6A|8|@]|D|@]|E|$]]|$1|24|3|25|5|6|7|6B|8|@]|D|@$9|6C|A|6D|1|6E]|$9|6F|A|6G|1|6H]|$9|6I|A|6J|1|6K]]|E|$]]|$1|26|3|-4|5|6|7|6L|8|@]|D|@]|E|$]]]|27|$28|$5|29|2A|2B|E|$2C|2D]]|2E|$5|29|2A|2B|E|$2C|2F]]|2G|$5|2H|2A|2I|E|$2J|2K|2L|-4]]|2M|$5|29|2A|2B|E|$2C|2N]]|2O|$5|29|2A|2B|E|$2C|2P]]|2Q|$5|29|2A|2B|E|$2C|2R]]|2S|$5|29|2A|2B|E|$2C|2T]]]]

First you have to understand what the <code>Podfile.lock</code> is then understand what the <code>Manifest.lock</code> is and where it's used.
The <code>Podfile</code> holds either the (<a href="https://stackoverflow.com/questions/20213751/what-is-the-usage-of-in-cocoapods">optimistic</a> or exact) versions of every dependency you have. The lock file holds only exact versions.
Once you do <code>pod install</code> all the pods get downloaded/installed into the <code>/pods</code> directory. You may want to commit them Or maybe not. That's up to your team. What's NOT up to your team is decide if they should commit the the <code>Podfile.lock</code> or not. That needs to be committed so every dev in the team can be sure they've got the exact same version.
<ul>
<li>So let's say you downloaded your team’s code. In your project's root directory you only have <code>Podfile</code> and <code>Podfile.lock</code> and the <code>Pods</code> directory wasn’t committed.</li>
<li>Then you do <code>pod install</code> to creat the <code>Pods</code> directory. Your snapshot of every pods’ version should match with the versions of all pods from the Podfile.lock.</li>
<li>CocoaPods has a safety check in place, to ensure matching versions</li>
</ul>
This is where the <code>Manifest.lock</code> comes into play. <code>Manifest.lock</code> is your local machine's lock created. It has to match with <code>Podfile.lock</code> that is generated by the last commit (that caused changes in for your pods) in your repo. If it doesn't match then something is messed up.
Docs on what the <a href="https://github.com/CocoaPods/CocoaPods/blob/master/lib/cocoapods/installer.rb#L21-L25" rel="nofollow noreferrer">Manifest.lock</a> file is:
<pre><code> # Manifest.lock: A file contained in the Pods folder that keeps track of
 # the pods installed in the local machine. This files is used once the
 # exact versions of the Pods has been computed to detect if that version
 # is already installed. This file is not intended to be kept under source
 # control and is a copy of the Podfile.lock.
</code></pre>
I honestly can only think of one scenario in which the <code>Manifest.lock</code> and <code>Podfile.lock</code> would be out of sync:
I mean if you pull from main branch, then you get main's <code>Podfile</code> and lock file. If you then make a change to the <code>Podfile</code> and then run <code>pod install</code>, then you would be updating the <code>Podfile.lock</code> and <code>Manifest.lock</code> and will keep them in sync. No issues with this
Is this just so that if:
<ol>
<li>You and your team don’t commit the <code>/Pods</code> directory</li>
<li>You have merge conflicts in your <code>Podfile</code> or <code>Podfile.lock</code> but don’t realize it. Or you haven't committed both <code>Podfile</code> and <code>Podfile.lock</code></li>
<li>Then given that Xcode doesn’t process the <code>Podfile</code> and <code>Podfile.lock</code>, then naturally your project can build successfully.</li>
<li>However if you go in an inspect your Build Phases of your targets you'd see the following</li>
</ol>
<a href="https://i.stack.imgur.com/emIB9.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/emIB9.png" alt="enter image description here" /></a>
That script is documented <a href="https://github.com/CocoaPods/CocoaPods/blob/master/lib/cocoapods/installer/user_project_integrator/target_integrator.rb#L587-L594" rel="nofollow noreferrer">here</a>
<pre><code># Adds a shell script build phase responsible for checking if the Pods
# locked in the Pods/Manifest.lock file are in sync with the Pods defined
# in the Podfile.lock.
# 
# @note The build phase is appended to the front because to fail fast.
# 
# @return [void]
</code></pre>
What those lines do are: perform a <code>diff</code> and ensure that sure your <code>Manifest.lock</code> i.e. your local snapshot of all installed pod versions are equal to <code>Podfile.lock</code> i.e. your repo's current snapshot of all installed pod versions.
The fix is likely super simple, just make sure you <code>Podfile</code> is what you want. Then just run <code>pod install</code>. You have also somehow accidentally made changes to your <code>Manifest.lock</code> inside your <code>/Pods</code> directory (or as mentioned earlier maybe only committed the lock file but not the <code>Podfile</code> or vice versa). Deleting <code>/Pods</code> directory causes no harm. Just do a <code>pod install</code> after. Do not do <code>pod update</code> unless that's what you want.
Just make sure you never delete the <code>Podfile.lock</code> otherwise if you do <code>pod install</code> then it would update all dependencies to the latest version it can.
<hr />
Also helpful to see and this <a href="https://www.youtube.com/watch?v=H-zK1mEwTe0" rel="nofollow noreferrer">video</a> on lock files, <a href="https://guides.cocoapods.org/using/pod-install-vs-update.html" rel="nofollow noreferrer">CocoaPods docs</a> on how the lock file is put to use differently for pod install vs. pod update and last see how all that logic is used in more detail
<a href="https://artsy.github.io/blog/2016/05/03/podspec-checksums/" rel="nofollow noreferrer">this artsy blog on checksums</a>. It's worth noting that a single space will create a new checksum and can make things out of sync.

blocks|key|162965|text|如果您使用Windows进行Git签出，并且Podfile.lock是使用windows+(CRLF)行结尾创建的，也会发生这种情况。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|162966|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

This can also happen if you use Windows for the Git checkout, and the Podfile.lock is created with windows (CRLF) line endings.

blocks|key|165347|text|对我来说，这是Ruby版本号的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|165348|我得到了一个错误：|165349|The+sandbox+is+not+in+sync+with+the+Podfile.lock.+Run+'pod+install'+or+update+your+CocoaPods+installation.|code-block|syntax|javascript|165350|在尝试了一百万种方法之后，包括这个线程中包含的大部分内容，我最终修改了位于：usr/local/bin/pod的pod文件|offset|length|style|CODE|165351|我更正了第一行，使其指向我的机器上实际存在的ruby版本。我改变了：|165352|#!/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/bin/ruby|165353|至|165354|#!/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/ruby|165355|经过几天的努力，将3改为6解决了一切问题。|165356|entityMap^0|0|0|0|12|H|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|12|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|13|8|@$K|14|L|15|M|N]]|9|@]|A|$]]|$1|O|3|P|5|6|7|16|8|@]|9|@]|A|$]]|$1|Q|3|R|5|F|7|17|8|@]|9|@]|A|$G|H]]|$1|S|3|T|5|6|7|18|8|@]|9|@]|A|$]]|$1|U|3|V|5|F|7|19|8|@]|9|@]|A|$G|H]]|$1|W|3|X|5|6|7|1A|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|Z|$]]

For me it was an issue with the Ruby version number.
I was getting the error:
<pre><code>The sandbox is not in sync with the Podfile.lock. Run 'pod install' or update your CocoaPods installation.
</code></pre>
After trying a million things, including much of what is included in this thread I wound up hacking the pod file located at: <code>usr/local/bin/pod</code>
I corrected the first line to point to the ruby version that actually existed on my machine. I changed:
<pre><code>#!/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/bin/ruby
</code></pre>
to
<pre><code>#!/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/ruby
</code></pre>
After days of struggling, changing a 3 to a 6 fixed everything.

blocks|key|2760052|text|我尝试了pod+install的各种组合，删除node_modules并重新安装，清理和重建xcode项目，甚至重启我的计算机。这些对我来说都不管用。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2760053|我的修复方法是在项目的根目录中运行pod+--version。我不知道这是怎么做到的，也不知道为什么，但它成功地安装了一个缺失的依赖项，所以我想在这里分享它，以防它对其他人有帮助:)|2760054|entityMap^0|4|B|N|C|0|H|D|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|R|8|@]|D|@]|E|$]]]|I|$]]

I tried all sorts of combinations of <code>pod install</code>, deleting <code>node_modules</code> &amp; reinstalling, cleaning &amp; rebuilding the xcode project, and even restarting my computer. None of these worked for me...
The fix for me was running <code>pod --version</code> in my project's root directory. I don't know how or why, but this successfully installed a missing dependency, so I thought I'd share it here in case it helps someone else :)

blocks|key|2972812|text|确保已设置pod配置文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2972813|​|2972814|📷|atomic|offset|length|2972815|2972816|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/54eebaf34fc279bcc396b5a7a6616ffc.png|imageAlt^0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@$G|V|H|W|1|X]]|A|$]]|$1|I|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q|R|-4]]]]

Be sure the pod configuration files are set.
<a href="https://i.stack.imgur.com/fvDhZ.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/fvDhZ.png" alt="enter image description here" /></a>

blocks|key|2760186|text|我可以通过点击Product->Clean+Build+Folder来修复这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2760187|​|2760188|📷|atomic|offset|length|2760189|2760190|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/1905b5782414edc2c638de97149b190b.png|imageAlt^0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@$G|V|H|W|1|X]]|A|$]]|$1|I|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q|R|-4]]]]

I was able to fix this by clicking Product-&gt;Clean Build Folder.
<a href="https://i.stack.imgur.com/YRIC6.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/YRIC6.png" alt="enter image description here" /></a>

blocks|key|167073|text|下面这些简单的步骤对我很有效：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|167074|请关闭您的工作区，然后运行pod+install+--repo-update|offset|length|style|CODE|167075|open+|unordered-list-item|167076|，|ordered-list-item|167077|(如果您清理您的构建文件夹，则会更合理)。|167078|167079|167080|entityMap^0|0|D|P|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@$D|V|E|W|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|X|8|@]|9|@]|A|$]]|$1|K|3|L|5|M|7|Y|8|@]|9|@]|A|$]]|$1|N|3|O|5|M|7|Z|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|10|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|11|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|S|$]]

These simple steps work for me:
<ol>
<li>close your workspace</li>
<li>run <code>pod install --repo-update</code></li>
<li>open your workspace, rebuild (It will be more reasonable, if you clean up your build folder).</li>
</ol>

blocks|key|2972892|text|在我的例子中，这个问题是由损坏的*.xcworkspace文件引起的。它在左侧的project+Navigator菜单中显示了我的项目的两个不同版本。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2972893|为了验证，我从位于Build+Phases+>+Check+Pods+Manifest.lock中的bash脚本中删除了输出重定向(+>+/dev/null)，以便它将diff输出到STDOUT.果然，在阅读构建日志时，我得到了截然不同的Podfile.lock和Manifest.lock输出。|2972894|为了解决这个问题，我删除了我的*.xcworkspace，然后从我的ios文件夹中再次运行pod+install。它会自动重新生成工作区文件。在XCode中打开新文件，就不会再有构建错误了。|2972895|entityMap^0|G|D|0|9|13|1V|B|0|F|D|Y|3|19|B|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|T|8|@$9|U|A|V|B|C]|$9|W|A|X|B|C]|$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|J|3|-4|5|6|7|10|8|@]|D|@]|E|$]]]|K|$]]

In my case, this problem was due to a corrupt <code>*.xcworkspace</code> file. It was showing two different versions of my project in the Project Navigator menu on the left.
To verify, I removed the output redirection (<code> &gt; /dev/null</code>) from the bash script located in <code>Build Phases &gt; Check Pods Manifest.lock</code>, so that it would print the diff to STDOUT. Sure enough, reading the build log, I had wildly different Podfile.lock and Manifest.lock output.
To fix it I deleted my <code>*.xcworkspace</code>, then ran <code>pod install</code> again from my <code>ios</code> folder. That autoregenerates the workspace file. Open that new file in XCode and voila, no more build errors.

blocks|key|2760270|text|检查Pods目标和Runner目标必须相同|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2760271|1-+Runner|2760272|​|2760273|📷|atomic|offset|length|2760274|2760275|2-+Pod|2760276|2760277|2760278|2760279|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/cbe332a3a26e4033ced27745a1897e7e.png|imageAlt|1|https://ask.qcloudimg.com/http-save/yehe-900000/122001c9abca0c03306e1332d05789e7.png^0|0|0|0|0|1|0|0|0|0|0|0|1|1|0|0^^$0|@$1|2|3|4|5|6|7|11|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|12|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|13|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|14|8|@]|9|@$I|15|J|16|1|17]]|A|$]]|$1|K|3|E|5|6|7|18|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|19|8|@]|9|@]|A|$]]|$1|N|3|E|5|6|7|1A|8|@]|9|@]|A|$]]|$1|O|3|G|5|H|7|1B|8|@]|9|@$I|1C|J|1D|1|1E]]|A|$]]|$1|P|3|E|5|6|7|1F|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X|Y|-4]]|Z|$5|T|U|V|A|$W|10|Y|-4]]]]

Check Pods target and Runner target thats have to be same
1- Runner
<a href="https://i.stack.imgur.com/GGMsO.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/GGMsO.png" alt="enter image description here" /></a>
2- Pods
<a href="https://i.stack.imgur.com/doQmf.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/doQmf.png" alt="enter image description here" /></a>

blocks|key|2760290|text|你能试试这个吗：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2760291|2760292|删除pod文件夹|ordered-list-item|2760293|删除pod+pod+install|2760294|Clean+%2B+Build|2760295|2760296|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|N|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|O|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|P|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|Q|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|L|$]]

Can you try this:
<ol>
<li>Delete the Pods folder</li>
<li>Delete Podfile.lock</li>
<li>Run pod install</li>
<li>Clean + Build</li>
</ol>

I've encounter an strange issue after installing RestKit with cocoapods.
after resolving RestKit dependency for my project with cocoapods and trying to build it, I face this error: 

<blockquote>
 The sandbox is not in sync with the Podfile.lock. Run 'pod install' or update your CocoaPods installation.
</blockquote>

I tried running <code>pod install</code>, but no change.

Here are some shots:
<img src="https://i.stack.imgur.com/mrTp5.png" alt="enter image description here">

<img src="https://i.stack.imgur.com/N5W2w.png" alt="enter image description here">

<pre><code> PODS:
 - AFNetworking (1.3.3)
 - RestKit (0.20.3):
 - RestKit/Core
 - RestKit/Core (0.20.3):
 - RestKit/CoreData
 - RestKit/Network
 - RestKit/ObjectMapping
 - RestKit/CoreData (0.20.3)
 - RestKit/Network (0.20.3):
 - AFNetworking (~&gt; 1.3.0)
 - RestKit/ObjectMapping
 - RestKit/Support
 - SOCKit
 - RestKit/ObjectMapping (0.20.3)
 - RestKit/Search (0.20.3):
 - RestKit/CoreData
 - RestKit/Support (0.20.3):
 - TransitionKit (= 1.1.1)
 - RestKit/Testing (0.20.3)
 - SOCKit (1.1)
 - TransitionKit (1.1.1)

DEPENDENCIES:
 - RestKit (~&gt; 0.20.0)
 - RestKit/Search (~&gt; 0.20.0)
 - RestKit/Testing (~&gt; 0.20.0)

SPEC CHECKSUMS:
 AFNetworking: 61fdd49e2ffe6380378df37b3b6e70630bb9dd66
 RestKit: 1f181c180105a92f11ec4f6cd7de37625e516d83
 SOCKit: 2f3bc4d07910de12dcc202815e07db68a3802581
 TransitionKit: d0e3344aac92991395d4c2e72d9c5a8ceeb12910

COCOAPODS: 0.29.0
</code></pre>

Error: "The sandbox is not in sync with the Podfile.lock..." after installing RestKit with cocoapods

Windows

Flutter

Cordova

Ionic

Swift

Xcode

在使用cocoapods安装RestKit之后，我遇到了一个奇怪的问题。在使用cocoapods为我的项目解析RestKit依赖项并尝试构建它之后，我遇到了这个错误：沙箱与Podfile.lock不同步。运行'pod install‘或更新您的CocoaPods安装。我尝试运行pod install，但没有任何变化。以...

问错误：“沙箱与Podfile.lock不同步...”在安装带有cocoapods的RestKit之后
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问错误：“沙箱与Podfile.lock不同步...”在安装带有cocoapods的RestKit之后EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问错误：“沙箱与Podfile.lock不同步...”在安装带有cocoapods的RestKit之后
EN