blocks|key|1443406|text|尝试使用pod+install+—repo-update，它可以解决您的问题。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1443407|entityMap^0|4|O|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

Try with <code>pod install —repo-update</code>, it could solve your problem.

blocks|key|1443412|text|您需要以下两个Firebase+SDKs的更高版本才能使用应用程序内消息传递|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1443413|pod+'Firebase/Database',+'~>+5.0.0'
pod+'Firebase/Messaging',+'~>+5.0.0'|code-block|syntax|javascript|1443414|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|$]]

You need higher versions of the following two Firebase SDKs to use in-app messaging

<pre><code>pod 'Firebase/Database', '~&gt; 5.0.0'
pod 'Firebase/Messaging', '~&gt; 5.0.0'
</code></pre>

blocks|key|111154|text|减少您的Podfile使其成为一个MCVE，我们可以简单地再现这个问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|111155|target+'MyProject'+do
++++pod+'Firebase/InAppMessagingDisplay'
end|code-block|syntax|javascript|111156|那么让我们来看一下规范：|111157|→https://cocoapods.org/pods/Firebase|111158|→https://github.com/CocoaPods/Specs/blob/master/Specs/0/3/5/Firebase/5.6.0/Firebase.podspec.json|111159|"FirebaseInAppMessaging":+"0.11.0"上的→依赖关系|style|CODE|111160|→https://cocoapods.org/pods/FirebaseInAppMessaging|111161|将https://firebase.google.com/docs/in-app-messaging/重定向到→|111162|这意味着Firebase/InAppMessagingDisplay依赖于谷歌删除的另一个规范。为证明移除：|111163|$+pod回购更新
$+pod搜索FirebaseInAppMessaging
好了！无法找到与FirebaseInAppMessaging匹配的名称、作者、摘要或描述的荚|blockquote|111164|但是这个规范是存在的，它是九天前(2018年8月16日，凌晨12:38+GMT%2B8)在：https://github.com/CocoaPods/Specs/blob/master/Specs/2/a/8/FirebaseInAppMessaging/0.11.0/FirebaseInAppMessaging.podspec.json添加的。所以有些人可能会把它藏起来。|111165|我建议你联系谷歌，问问他们什么时候恢复FirebaseInAppMessaging。同时，你不能使用它。|111166|entityMap|0|LINK|mutability|MUTABLE|url|/help/mcve|1|https://cocoapods.org/pods/Firebase|2|https://github.com/CocoaPods/Specs/blob/master/Specs/0/3/5/Firebase/5.6.0/Firebase.podspec.json|3|https://cocoapods.org/pods/FirebaseInAppMessaging|4|https://firebase.google.com/docs/in-app-messaging/|5|https://github.com/CocoaPods/Specs/blob/master/Specs/2/a/8/FirebaseInAppMessaging/0.11.0/FirebaseInAppMessaging.podspec.json^0|H|4|0|0|0|0|1|Z|1|0|1|2N|2|0|0|Y|0|1|1D|3|0|1|1E|4|0|4|U|0|1C|M|0|18|3G|5|0|J|M|0^^$0|@$1|2|3|4|5|6|7|1N|8|@]|9|@$A|1O|B|1P|1|1Q]]|C|$]]|$1|D|3|E|5|F|7|1R|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|1S|8|@]|9|@]|C|$]]|$1|K|3|L|5|6|7|1T|8|@]|9|@$A|1U|B|1V|1|1W]]|C|$]]|$1|M|3|N|5|6|7|1X|8|@]|9|@$A|1Y|B|1Z|1|20]]|C|$]]|$1|O|3|P|5|6|7|21|8|@$A|22|B|23|Q|R]]|9|@]|C|$]]|$1|S|3|T|5|6|7|24|8|@]|9|@$A|25|B|26|1|27]]|C|$]]|$1|U|3|V|5|6|7|28|8|@]|9|@$A|29|B|2A|1|2B]]|C|$]]|$1|W|3|X|5|6|7|2C|8|@$A|2D|B|2E|Q|R]]|9|@]|C|$]]|$1|Y|3|Z|5|10|7|2F|8|@$A|2G|B|2H|Q|R]]|9|@]|C|$]]|$1|11|3|12|5|6|7|2I|8|@]|9|@$A|2J|B|2K|1|2L]]|C|$]]|$1|13|3|14|5|6|7|2M|8|@$A|2N|B|2O|Q|R]]|9|@]|C|$]]|$1|15|3|-4|5|6|7|2P|8|@]|9|@]|C|$]]]|16|$17|$5|18|19|1A|C|$1B|1C]]|1D|$5|18|19|1A|C|$1B|1E]]|1F|$5|18|19|1A|C|$1B|1G]]|1H|$5|18|19|1A|C|$1B|1I]]|1J|$5|18|19|1A|C|$1B|1K]]|1L|$5|18|19|1A|C|$1B|1M]]]]

Reducing your Podfile to make it an <a href="/help/mcve">MCVE</a>, we can reproduce the issue with simply:

<pre><code>target 'MyProject' do
 pod 'Firebase/InAppMessagingDisplay'
end
</code></pre>

So let's look at the specs:

→ <a href="https://cocoapods.org/pods/Firebase" rel="nofollow noreferrer">https://cocoapods.org/pods/Firebase</a> 
→ <a href="https://github.com/CocoaPods/Specs/blob/master/Specs/0/3/5/Firebase/5.6.0/Firebase.podspec.json" rel="nofollow noreferrer">https://github.com/CocoaPods/Specs/blob/master/Specs/0/3/5/Firebase/5.6.0/Firebase.podspec.json</a> 
→ Dependency on <code>"FirebaseInAppMessaging": "0.11.0"</code> 
→ <a href="https://cocoapods.org/pods/FirebaseInAppMessaging" rel="nofollow noreferrer">https://cocoapods.org/pods/FirebaseInAppMessaging</a> 
→ Redirection to <a href="https://firebase.google.com/docs/in-app-messaging/" rel="nofollow noreferrer">https://firebase.google.com/docs/in-app-messaging/</a>

Which means <code>Firebase/InAppMessagingDisplay</code> has a dependency on another spec that got REMOVED by Google. To demonstrate the removal:

<blockquote>
 $ pod repo update 
 $ pod search FirebaseInAppMessaging 
 [!] Unable to find a pod with name, author, summary, or description matching <code>FirebaseInAppMessaging</code>
</blockquote>

But this spec exists, it was added nine days ago (Aug 16, 2018, 12:38 AM GMT+8) at: <a href="https://github.com/CocoaPods/Specs/blob/master/Specs/2/a/8/FirebaseInAppMessaging/0.11.0/FirebaseInAppMessaging.podspec.json" rel="nofollow noreferrer">https://github.com/CocoaPods/Specs/blob/master/Specs/2/a/8/FirebaseInAppMessaging/0.11.0/FirebaseInAppMessaging.podspec.json</a>. So some people may have it in cache.

I suggest you contact Google and ask them when they will restore <code>FirebaseInAppMessaging</code>. In the mean time, you can't use it.

blocks|key|112033|text|pod+'Firebase/Core',+'~>+5.7.0'
pod+'Firebase/InAppMessagingDisplay'|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|112034|为我工作过。|unstyled|112035|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|J|8|@]|9|@]|A|$]]|$1|G|3|-4|5|F|7|K|8|@]|9|@]|A|$]]]|H|$]]

<pre><code>pod 'Firebase/Core', '~&gt; 5.7.0'
pod 'Firebase/InAppMessagingDisplay'
</code></pre>

Worked for me.

blocks|key|1443502|text|我找到了解决这个问题的办法。我的文件看起来像你的。我一直在破解豆荚的依赖性，我发现我使用的是一个旧的参考谷歌分析。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1443503|我使用的是pod+'Google/Analytics'而不是pod+'GoogleAnalytics'。有一次，我改变了可可豆的引用，遵循谷歌发布的豆荚列表，一切都很好。|offset|length|style|CODE|1443504|谷歌发布的豆荚列表|1443505|entityMap|0|LINK|mutability|MUTABLE|url|https://developers.google.com/ios/guides/cocoapods^0|0|5|M|U|L|0|0|9|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@$D|T|E|U|F|G]|$D|V|E|W|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@$D|Y|E|Z|1|10]]|A|$]]|$1|J|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

I found a solution to this issue. My podfile was looking like yours. I have been cracking the pods dependencies and I found I was using an old reference for Google Analytics. 

I was using <code>pod 'Google/Analytics'</code> instead of <code>pod 'GoogleAnalytics'</code>.
Once I changed the cocoa pods reference following the list of pods published by Google everything worked fine.

<a href="https://developers.google.com/ios/guides/cocoapods" rel="nofollow noreferrer">Pods list published by Google</a>

I'm having difficulties installing Firebase new feature "In-App Messaging".
When trying to run <code>pod install</code> on the project, I get this error:

<pre><code>[!] CocoaPods could not find compatible versions for pod "Firebase/InAppMessagingDisplay":
 In Podfile:
 Firebase/InAppMessagingDisplay

Specs satisfying the `Firebase/InAppMessagingDisplay` dependency were found, but they required a higher minimum deployment target.
</code></pre>

These are the pod files in my project:

<pre><code>target 'MyProject' do
 platform :ios, '10.1'
 inhibit_all_warnings!
 use_frameworks!

 pod 'AlamofireImage', '~&gt; 3.1'
 pod 'AKPickerView-Swift', :git =&gt; 'https://github.com/Akkyie/AKPickerView-Swift.git', :inhibit_warnings =&gt; true
 pod 'Firebase/Database', '~&gt; 5.0.0'
 pod 'Firebase/Messaging', '~&gt; 5.0.0'
 pod 'Firebase/Core'
 pod 'Firebase/Auth'
 pod 'Firebase/RemoteConfig'
 pod 'Firebase/InAppMessagingDisplay'
 pod 'Google/Analytics'
 pod 'Protobuf', '~&gt; 3.2', :inhibit_warnings =&gt; true
 pod 'PromiseKit/CoreLocation', '~&gt; 4.1'
 pod 'GoogleConversionTracking'
 pod 'FBSDKCoreKit'
 pod 'Branch'
 pod 'Fabric'
 pod 'Crashlytics'
 pod 'Apply'
 pod 'SnapKit', '&gt;= 4.0.0'
 pod 'KeychainSwift', '~&gt; 10.0'
 pod 'Bond'
end
</code></pre>

I've read other questions in here and tried two different solutions.
First I tried this:
1. <code>pod repo remove master</code>
2. <code>pod setup</code>
3. <code>pod install</code>
Which didn't work. Got the same error.

Then I tried this:
1. <code>pod repo update</code>
2. <code>pod deintegrate</code>
3. <code>pod install</code>
With the same result.

Have any of you experienced this and know a solution?

Firebase pod 'InAppMessagingDisplay'

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我在安装Firebase新功能"In-App Messaging“时遇到了困难。当试图在项目上运行pod install时，我会得到以下错误：[!] CocoaPods could not find compatible versions for pod "Firebase/InAppMessagingDisplay"...

问火柴盒'InAppMessagingDisplay‘
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问火柴盒'InAppMessagingDisplay‘EN