CocoaPods没有将FirebaseSDK更新到4.0.0版-CocoaPodsnotupdatingFirebaseSDKtoVersion4.0.0

18  

There was nothing wrong with your original Podfile ;) You are just confusing pod install with pod update — you were running the former but you should be using the latter instead. A brief overview to clear things up:

您的原始Podfile没有任何问题;）您只是将pod安装与pod更新混淆 - 您运行的是前者，但您应该使用后者。清理简要概述：

pod install. When you run pod install, it only resolves dependencies for pods that are not already listed in the Podfile.lock. For pods in Podfile.lock, it downloads the explicit version listed there, without checking if a newer version is available — I believe this (expected) behavior was causing your issue.

pod安装。运行pod安装时，它仅解析Podfile.lock中尚未列出的pod的依赖项。对于Podfile.lock中的pod，它会下载那里列出的显式版本，而不检查是否有更新的版本 - 我相信这种（预期的）行为导致了您的问题。

pod update. If you run pod update, CocoaPods will update every pod listed in your Podfile to the latest version possible. Of course, respecting the version restrictions declared in your Podfile, if any.

pod更新。如果您运行pod更新，CocoaPods会将Podfile中列出的每个pod更新为最新版本。当然，尊重Podfile中声明的版本限制（如果有）。

For more information, be sure to check the pod install vs. pod update guide as well.

有关详细信息，请务必查看pod install与pod更新指南。

11  

I had a similar issue and was stuck at the following output even after running the run pod repo remove master and pod install and pod update:

我有一个类似的问题，即使在运行pod pod repo删除master和pod install和pod update之后，仍然停留在以下输出：

Using AmazonAd (2.2.15)
Using Firebase (3.17.0)
Using FirebaseAnalytics (3.9.0)
Using FirebaseCore (3.6.0)
Using FirebaseInstanceID (1.0.10)
Using Google (3.1.0)
Using Google-Mobile-Ads-SDK (7.19.1)
Using GoogleToolboxForMac (2.1.1)

I kept seeing the note in the pod update command output:

我一直看到pod update命令输出中的注释：

[!] Google has been deprecated

So I deleted the Google from the podfile:

所以我从podfile中删除了Google：

 pod Google

Then I re-ran:

然后我重新跑了：

 pod update

and Received:

并收到：

Using AmazonAd (2.2.15)
Installing Firebase 4.3.0 (was 3.17.0)
Installing FirebaseAnalytics 4.0.4 (was 3.9.0)
Installing FirebaseCore 4.0.8 (was 3.6.0)
Installing FirebaseInstanceID 2.0.4 (was 1.0.10)
Installing Google-Mobile-Ads-SDK 7.24.1 (was 7.19.1)
Using GoogleToolboxForMac (2.1.1)
Installing nanopb (0.3.8)

3  

Similarly to how Alamofire in my original podfile states the version I would like, doing so for firebase made it update to version 4.0.0 and the appropriate firebase functions work now.

与原始podfile中的Alamofire如何声明我想要的版本类似，对firebase执行此操作使其更新到版本4.0.0并且相应的firebase函数现在可以正常工作。

For example:

例如：

Change (for each):

改变（每个）：

pod 'Firebase/Auth'

To:

至：

pod 'Firebase/Auth', '~> 4.0.0'

A full example of my new podfile and the output after running pod install is as follows.

我的新podfile的完整示例和运行pod install后的输出如下所示。

Correct Podfile:

正确的Podfile：

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


target 'myProject' do

pod 'Firebase', '~> 4.0.0'
pod 'Firebase/Auth', '~> 4.0.0'
pod 'Firebase/Core', '~> 4.0.0'
pod 'Firebase/Storage', '~> 4.0.0'
pod 'Firebase/Database', '~> 4.0.0'
pod 'Firebase/Crash', '~> 4.0.0'
pod 'Firebase/Messaging', '~> 4.0.0'


pod 'Alamofire', '~> 4.4'

end

Output

产量

Analyzing dependencies
Downloading dependencies
Using Alamofire (4.4.0)
Using Firebase (4.0.0)
Using FirebaseAnalytics (4.0.0)
Using FirebaseAuth (4.0.0)
Using FirebaseCore (4.0.0)
Using FirebaseCrash (2.0.0)
Using FirebaseDatabase (4.0.0)
Using FirebaseInstanceID (2.0.0)
Using FirebaseMessaging (2.0.0)
Using FirebaseStorage (2.0.0)
Using GTMSessionFetcher (1.1.10)
Using GoogleToolboxForMac (2.1.1)
Using Protobuf (3.3.0)
Generating Pods project
Integrating client project
Sending stats
Pod installation complete! There are 8 dependencies from the Podfile and 13 total pods installed

2  

I had the same problem and just fixed it by changing the pod subsec into the full name of the pods like this:

我有同样的问题，只是通过将pod subsec更改为pod的全名来修复它，如下所示：

-    pod 'Firebase/Core'
-    pod 'Firebase/RemoteConfig'
+    pod 'FirebaseCore', '4.0.9'
+    pod 'FirebaseRemoteConfig', '2.0.3'

Rather weird that this confusion happened in the first place but at least this fixes it.

相当奇怪的是，这种混乱首先发生了，但至少可以解决这个问题。