我把pod文件里的pod从目标移到了外面。文件更改如下:

# Uncomment this line to define a global platform for your project
# platform :ios, '8.0'
# Uncomment this line if you're using Swift
use_frameworks!

target 'MyProject' do

pod 'Firebase', '>= 2.5.0'
pod 'Onboard'
pod 'GoogleMaps'
pod 'IQDropDownTextField'

end

:

# Uncomment this line to define a global platform for your project
# platform :ios, '8.0'
# Uncomment this line if you're using Swift
use_frameworks!

pod 'Firebase', '>= 2.5.0'
pod 'Onboard'
pod 'GoogleMaps'
pod 'IQDropDownTextField'

target 'MyProject' do

end

播客文件中产生问题的行是: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

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

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

为了解决这个问题，我:

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

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

这是我在运行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 酒吧得到 圆荚体安装

这发生在我身上是因为我已经有了Pod配置。我是iOS开发的新手，在搜索安装Alamofire + SwiftyJSON的说明时，无意中安装了不止一次库。对我来说，起作用的是:在“Pods”项目的“目标支持文件”文件夹中，我选择了两个正确的。xcconfig文件，并将它们拖到我的应用程序项目的“Pods”文件夹中。这允许在基本配置上选择正确的配置文件。

但是，如果我再次运行“pod install”，警告将更改为先前的.xcconfig文件。我试图从主项目中删除文件和旧的框架，但当我再次运行前面的命令时，给了我同样的警告，并在我的应用程序项目的“Pods”文件夹下创建文件“Pods.framework”。我忽略了它，尽管有两个框架，但它似乎运行正常。我不知道这是否正确，如果存在解决方案，它将受到欢迎。

我错了:

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.

我只是检查了我安装吊舱的路径，并纠正了它，重新安装，它只是工作。

确保在.xcodeproj或.xcworkspace(如果已经存在的话)存在的位置前面给出路径。