- html - 出于某种原因,IE8 对我的 Sass 文件中继承的 html5 CSS 不友好?
- JMeter 在响应断言中使用 span 标签的问题
- html - 在 :hover and :active? 上具有不同效果的 CSS 动画
- html - 相对于居中的 html 内容固定的 CSS 重复背景?
pod update --verbose 未完成,挂起。
CDN: trunk Relative path: Specs/7/4/b/GoogleToolboxForMac/2.1.2/GoogleToolboxForMac.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/7/4/b/GoogleToolboxForMac/2.1.3/GoogleToolboxForMac.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/7/4/b/GoogleToolboxForMac/2.1.4/GoogleToolboxForMac.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/7/4/b/GoogleToolboxForMac/2.2.0/GoogleToolboxForMac.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/7/4/b/GoogleToolboxForMac/2.2.1/GoogleToolboxForMac.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/d/4/0/GoogleSignIn/4.4.0/GoogleSignIn.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/d/4/0/GoogleSignIn/4.3.0/GoogleSignIn.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/d/4/0/GoogleSignIn/4.2.0/GoogleSignIn.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/0/3/5/Firebase/3.7.0/Firebase.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/0/3/5/Firebase/3.6.0/Firebase.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/e/2/1/FirebaseAnalytics/3.9.0/FirebaseAnalytics.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/e/2/1/FirebaseAnalytics/3.8.0/FirebaseAnalytics.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/e/2/1/FirebaseAnalytics/3.7.0/FirebaseAnalytics.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/e/2/1/FirebaseAnalytics/3.6.0/FirebaseAnalytics.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/e/2/1/FirebaseAnalytics/3.5.1/FirebaseAnalytics.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/e/2/1/FirebaseAnalytics/3.4.4/FirebaseAnalytics.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/e/2/1/FirebaseAnalytics/3.4.3/FirebaseAnalytics.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/e/2/1/FirebaseAnalytics/3.4.2/FirebaseAnalytics.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/e/2/1/FirebaseAnalytics/3.3.1/FirebaseAnalytics.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/e/2/1/FirebaseAnalytics/3.3.0/FirebaseAnalytics.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/e/2/1/FirebaseAnalytics/3.2.1/FirebaseAnalytics.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/e/2/1/FirebaseAnalytics/3.2.0/FirebaseAnalytics.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/e/2/1/FirebaseAnalytics/5.8.0/FirebaseAnalytics.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/e/3/b/GoogleAppMeasurement/5.8.0/GoogleAppMeasurement.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/e/2/1/FirebaseAnalytics/3.9.0/FirebaseAnalytics.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/e/2/1/FirebaseAnalytics/3.8.0/FirebaseAnalytics.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/e/2/1/FirebaseAnalytics/3.7.0/FirebaseAnalytics.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/e/2/1/FirebaseAnalytics/3.6.0/FirebaseAnalytics.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/e/2/1/FirebaseAnalytics/3.5.1/FirebaseAnalytics.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/e/2/1/FirebaseAnalytics/3.4.4/FirebaseAnalytics.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/e/2/1/FirebaseAnalytics/3.4.3/FirebaseAnalytics.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/e/2/1/FirebaseAnalytics/3.4.2/FirebaseAnalytics.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/0/9/f/FirebaseFirestore/1.2.0/FirebaseFirestore.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/0/9/f/FirebaseFirestore/1.2.0/FirebaseFirestore.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/8/b/d/FirebaseCore/5.4.0/FirebaseCore.podspec.json exists! Returning local because checking is only perfomed in repo update
播客文件
# Uncomment the next line to define a global platform for your project
platform :ios, '9.0'
target 'ALLIPONews' do
# Comment the next line if you're not using Swift and don't want to use dynamic frameworks
use_frameworks!
pod 'Firebase'
pod 'Firebase/Core' #Prerequisite Libraries and Analytics
#pod 'Firebase/AdMob' #AdMob
pod 'Firebase/Messaging' #Cloud Messaging /
pod 'Firebase/Database' #Realtime Database
pod 'Firebase/Invites' #Invites
pod 'Firebase/DynamicLinks' #Dynamic Links
pod 'Firebase/RemoteConfig' #Remote Config
pod 'Firebase/Auth' #Authentication
pod 'Firebase/Storage' #Storage
pod 'Firebase/Performance' #Performance Monitoring
pod 'Firebase/Firestore' #Firestore
pod 'FirebaseUI/Database'
pod 'GoogleSignIn'
pod 'MBProgressHUD'
pod 'SDWebImage'
pod 'SDWebImage/WebP'
pod 'SDWebImage/GIF'
pod 'Alamofire'
pod 'AlamofireImage'
pod 'PageMenu'
pod 'RMessage'
pod 'SwiftyJSON'
pod 'FreshchatSDK'
pod 'TwitterCore'
pod 'TwitterKit'
pod 'SwiftLocation'
pod 'SwiftDate'
pod 'GzipSwift'
pod 'DataCompression'
pod 'GoogleMaps'
pod 'GooglePlaces'
pod 'PDFReader'
#Analytics
pod 'Branch'
pod 'Fabric'
pod 'Crashlytics'
pod 'Mixpanel-swift'
#Contacts
#pod 'APAddressBook/Swift'
pod 'SwiftAddressBook'
#Logging
pod 'CocoaLumberjack/Swift'
#UI
pod 'Material'
pod 'Motion'
#pod 'LTMorphingLabel'
#pod 'CountdownLabel'
pod 'expanding-collection' #Ramotion
pod 'paper-onboarding' #Ramotion
#pod 'RAMAnimatedTabBarController' #Ramotion
#pod 'FoldingCell' #Ramotion
pod 'SwiftMessages'
#pod 'MaterialComponents' #Google
pod 'Armchair'
pod 'UICircularProgressRing'
#pod 'CariocaMenu', '~> 2.0'
#Debugging
pod 'GDPerformanceView-Swift'
pod 'FlowUpIOSSDK', '~> 0.0.3'
#Animation
pod 'lottie-ios'
#User Data
pod 'DeviceKit'
pod 'TrueSDK'
#Charts
#pod 'ScrollableGraphView'
#Upgrades
pod 'Appgrades'
pod 'Siren'
#Javascript
pod 'WKWebViewJavascriptBridge', '~> 1.1.0'
#Chat
pod 'SendBirdSDK'
# Pods for ALL-IPO-NEWS
target 'ALLIPONewsTests' do
inherit! :complete
end
end
post_install do |installer|
installer.pods_project.targets.each do |target|
target.build_configurations.each do |config|
config.build_settings['SWIFT_VERSION'] = '5.0'
end
end
end
最佳答案
从 CocoaPods 1.8+ 开始,默认的 spec repo 更改为 CDN 而不是 Git。这对很多开发者来说都是个问题。
您可以通过将 source 'https://github.com/CocoaPods/Specs.git'
添加到您的 Podfile 顶部来配置 CocoaPods 以返回使用 Git 规范存储库
,这可能会有所帮助。
关于ios - pod update --verbose & pod install --verbose 未完成,挂起,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/58195252/
pod update --verbose 未完成,挂起。 CDN: trunk Relative path: Specs/7/4/b/GoogleToolboxForMac/2.1.2/Googl
我正在导入 Carbon进入我的 PowerShell 脚本;但是,当使用 -Verbose 运行我的脚本时,Carbon 也会输出很多 VERBOSE 语句。 是否可以静默导入模块,以便我可以忽略导
我正在创建一个调用Write-Verbose的.ps1脚本。我希望能够启用/禁用这些功能。 我希望调用脚本时可以传递-Verbose标志,并且一切正常。不幸的是,事实并非如此。 详细消息不会写出到主机
我们正在尝试用我们的 WAS(Websphere 应用程序服务器)实例调试一些严重的类加载器问题。 为此,我们提供了选项 -verbose:class 以查看 WAS 从何处加载哪个类。 对于大多数类
Powershell 中详细输出的默认颜色(例如 Write-Verbose 或 -Verbose 开关)是黄色的。这使其看起来像警告,尽管它并不重要。 如何更改详细输出的默认颜色? 最佳答案 这是可
根据回答like this one和我自己的经验,Powershell 可以自动传播 -Verbose(和 -Debug),非常方便。但是,当我想要将详细程度传播到的函数位于模块中时,这将停止工作。用
有没有一种简单的方法可以让 -Verbose 切换到 Powershell 中的其他函数调用“直通”? 我知道我可以在 $PSBoundParameters 中搜索标志并执行 if 语句: [Cmdl
也许在 PowerShell 中没有办法做到这一点。 如果我有文件 verboseTest.ps1 [CmdletBinding()] # CmdletBinding attribute ena
考虑重新设计数据库。想知道与以下内容有什么区别/注意事项: users fields ----- ------ id id user_id
我有一个冗长的 (re.X) 标记的正则表达式抛出异常,即使它看起来等同于它的压缩版本。 (我从后者构建了前者。) 精简版: import re test = 'catdog' test2 = 'do
我运行了这个测试脚本: use strict; use warnings; use Test::More tests => 3; use Carp; ok(1<2); pass(); fail();
我正在制作一个小型系统,我希望能够在整个系统中切换“详细”文本输出。 我创建了一个名为 globals.h 的文件: namespace REBr{ extern bool console_v
因此,我有一个包含大量调试输出的脚本,我可以使用 -v 标志打开/关闭这些输出。我当前的代码如下所示: def vprint( obj ): if args.verbose:
我知道 ansible -vvv 选项,但我不想看到所有命令的详细输出,我只想在任务失败时查看详细信息。 我怎样才能做到这一点? 附言。请提供可扩展的解决方案,必须编辑每个任务没有任何意义。 最佳答案
我正在使用 ant -f build.xml 运行一个 ant 脚本。该脚本应该编译我的项目并生成一个 jar 文件,但是在 ant 开始生成 jar 文件几秒钟后,该项目被终止,我在控制台中看到的只
我刚刚开始构建我的第一个 Rakefile(makefile 的 Ruby 版本),我想使用详细模式(如 makefile -V 或 bash -x)轻松调试我的脚本,是否有这样做的选项 ruby ?
本文整理了Java中org.zeromq.ZLoop.verbose()方法的一些代码示例,展示了ZLoop.verbose()的具体用法。这些代码示例主要来源于Github/Stackoverflo
我希望我的 ROS 包中的特定节点在 DEBUG 详细级别显示输出,而其他节点在 INFO 级别显示。我知道 rosconsole configuration file ,并且能够为包设置详细程度:
MS SQL Server 是否有一些配置选项可以启用更详细的错误消息。 具体示例:我想查看在插入期间违反约束的插入记录的实际字段值,以帮助追踪我无法重现的存储过程中的错误。 最佳答案 我不相信有任何
我正在学习 Coq 和我正在学习的书,( CPDT )大量使用了 auto在证明中。 由于我正在学习,因此我认为了解确切内容可能对我有帮助 auto在幕后做(越早越好)。有没有办法强制它准确显示它用来
我是一名优秀的程序员,十分优秀!