对于那些来自Flutter世界的人来说，这是一条误导性的错误消息，建议执行不必要的操作，正确的做法是忽略错误并使用Flutter cli(而不是pod)，如https://github.com/flutter/flutter/issues/73845:中所述

Gatzsche说，更好的信息应该是:

在颤振吊舱安装不应手动调用。运行pod install 执行以下命令颤振清除，颤振pub get和 颤振构建ios。

杰马格曼指出：

正如您所指出的，错误消息建议执行不必要的操作。颤振命令抑制来自吊舱的消息。您直接运行pod，这不是一个推荐的工作流。我们无法控制来自CocoaPods的错误消息，并且flutter命令行工具已经抑制了令人困惑的消息。

所以对我来说，这个问题是由于前面提到的xcconfig文件名在Swift 3更新发生之前被更改了。

有些东西是不同步的，所以Cocoapods创建了一个“恢复引用”文件夹部分与旧的命名文件，并链接到它们。

为了解决这个问题，我:

删除了“恢复的引用”文件夹和包含旧的 Xcode和文件系统中的.xcconfig文件 Xcode辞职 运行pod安装

从那以后，一切都为我处理好了，警告也消失了。

播客文件中产生问题的行是:link_with ['BluePlaquesLondon'， 'BluePlaquesLondonFramework']。

只是让这个:link_with ['BluePlaquesLondon']或这个(在我的情况下工作，希望它会在你的:-)):

source 'https://github.com/CocoaPods/Specs.git'
platform :ios, '8.0'

xcodeproj 'BluePlaquesLondon.xcodeproj'
inhibit_all_warnings!
link_with ['BluePlaquesLondon']

def import_pods

     pod 'TTTAttributedLabel', '~> 1.10.1'
     pod 'GoogleAnalytics-iOS-SDK', '~> 3.0.9'
     pod 'Google-Maps-iOS-SDK'
     pod 'IntentKit'
     pod 'HCViews'
     pod 'SVProgressHUD', :head
     pod 'iRate'
     pod 'iOS-KML-Framework', :git => 'https://github.com/FLCLjp/iOS-KML-Framework.git'

end

import_pods

target "BluePlaquesLondonFramework" do
    import_pods
    pod 'Kiwi'
end

这是我在运行pod安装或pod更新后得到的消息:

[!] CocoaPods did not set the base configuration of your project because your project already has a custom config set. In order for CocoaPods integration to work at all, please either set the base configurations of the target `Runner` to `Target Support Files/Pods-Runner/Pods-Runner.debug-staging.xcconfig` or include the `Target Support Files/Pods-Runner/Pods-Runner.debug-staging.xcconfig` in your build configuration (`Flutter/Debug.xcconfig`).

[!] CocoaPods did not set the base configuration of your project because your project already has a custom config set. In order for CocoaPods integration to work at all, please either set the base configurations of the target `Runner` to `Target Support Files/Pods-Runner/Pods-Runner.release-staging.xcconfig` or include the `Target Support Files/Pods-Runner/Pods-Runner.release-staging.xcconfig` in your build configuration (`Flutter/Release.xcconfig`).

[!] CocoaPods did not set the base configuration of your project because your project already has a custom config set. In order for CocoaPods integration to work at all, please either set the base configurations of the target `Runner` to `Target Support Files/Pods-Runner/Pods-Runner.profile-staging.xcconfig` or include the `Target Support Files/Pods-Runner/Pods-Runner.profile-staging.xcconfig` in your build configuration (`Flutter/Release.xcconfig`).

下面是我解决这个问题的方法:

将方案添加到项目“Runner”下的Podfile

project 'Runner', {
  'Debug' => :debug,
  'Debug-staging' => :debug,
  'Profile' => :release,
  'Profile-staging' => :release,
  'Release' => :release,
  'Release-staging' => :release,
}

进入ios/颤振/调试。Xcconfig和include

#include "Pods/Target Support Files/Pods-Runner/Pods-Runner.debug-staging.xcconfig"

进入ios/Flutter/Release。Xcconfig和include

#include "Pods/Target Support Files/Pods-Runner/Pods-Runner.release-staging.xcconfig"
#include "Pods/Target Support Files/Pods-Runner/Pods-Runner.profile-staging.xcconfig"

颤振清洁 删除podfile.lock 酒吧得到 圆荚体安装

对于那些来自Flutter世界的人来说，这是一条误导性的错误消息，建议执行不必要的操作，正确的做法是忽略错误并使用Flutter cli(而不是pod)，如https://github.com/flutter/flutter/issues/73845:中所述

Gatzsche说，更好的信息应该是:

在颤振吊舱安装不应手动调用。运行pod install 执行以下命令颤振清除，颤振pub get和 颤振构建ios。

杰马格曼指出：

正如您所指出的，错误消息建议执行不必要的操作。颤振命令抑制来自吊舱的消息。您直接运行pod，这不是一个推荐的工作流。我们无法控制来自CocoaPods的错误消息，并且flutter命令行工具已经抑制了令人困惑的消息。

别瞎捣鼓了，重置。

循序渐进的

显示项目导航器 选择项目 选择信息 在Configurations中，选择每个目标，一次一个(Debug, ApplicationUnitTest, Release，等等)，对于每个目标，将configuration设置为None。 确保“基于配置文件”为每个配置读取0配置集或无配置集。这是关键所在。 Xcode辞职 rm -rf Pods/ Podfile。锁;圆荚体安装

一旦你允许pod安装在第7步中发挥它的魔力，你就可以使用自定义配置并更改配置。