首页 文章

手动添加时解析firebase-crash链接器问题所需的库

提问于
浏览
-1

添加了Linking error on Firebase 3.7.0 for iOS Application中提到的库,但我仍然遇到链接器错误,因为添加了firebase崩溃 .

FIRLogError”,从参考: - 在FirebaseCrash(FCRBreakpadController_bc3acad0fa3a54a5c7c331f54af621b0.o)[FCRBreakpadController enableDebugger] - [FCRBreakpadController startWithConfiguration:]在FirebaseCrash(FCRBreakpadController_bc3acad0fa3a54a5c7c331f54af621b0.o) - [FCRBreakpadController createDirectory:]在FirebaseCrash(FCRBreakpadController_bc3acad0fa3a54a5c7c331f54af621b0.o)[FCRAnalytics messageDictionaryFromMessage: ]在FirebaseCrash(FCRAnalytics_281d4dbe093b1d2a74ef0873d1ac6263.o) - [FCRClient startWithConfiguration:错误:]在FirebaseCrash(FCRClient_482ceec6b5943edbfb1d1dff6beb18f6.o) - [FCRCrashDump crashInfoFromSystemMetadata:]在FirebaseCrash(FCRCrashDump_ee5f791af340383d1b426338c1150e39.o) - [FCRUploadQueue initWithDirectory:MAXSIZE:]在FirebaseCrash(FCRUploadQueue_2ce78e78dbb8f27676bd42e0302357a3.o )...... “FIRLogInfo”,从引用: - [FCRClient startWithConfiguration:错误:在FirebaseCrash(FCRClient_482ceec6b5943edbfb1d1dff6beb18f6.o)_ 49- [FCRBulkUploader了loadFileFromQueue:的onSuccess:] _ block_invoke在FirebaseCrash(FCRBulkUploader_af76d0815dcb863205f4ed96c30df68e.o) “_GSDK_objc_getClass”,从引用:在FirebaseCrash(FCRAnalytics_281d4dbe093b1d2a74ef0873d1ac6263.o)_____GetFIRAnalyticsClass_block_invoke “_OBJC_CLASS _ $ _ FIRApp”,从引用:在NFAppDelegate.o objc-类 - objc级-REF在FirebaseCrash(FCRClient_482ceec6b5943edbfb1d1dff6beb18f6.o)参考 “_OBJC_CLASS _ $ _ FIRInstanceID”,从引用:在FirebaseCrash(FCRCrashUploader_810ae32cc5e6c7f23936333033b9ebd7.o)objc级-REF “_OBJC_CLASS _ $ _ GSDK_PBDescriptor”,从引用:objc级-REF在FirebaseCrash(Sdk.pb_8328b2bef1af4d0941a97cc98e810c6c . O) “_OBJC_CLASS _ $ _ GSDK_PBGeneratedMessage”,从引用:_OBJC_CLASS _ $ _ FCRMSGTimestamp在FirebaseCrash(Sdk.pb_8328b2bef1af4d0941a97cc98e810c6c.o)_OBJC_CLASS _ $ _在FirebaseCrash(Sdk.pb_8328b2bef1af4d0941a97cc98e810c6c.o FCRMSGCrashReport)_OBJC_CLASS _ $ _ FCRMSGDevice在FirebaseCrash(Sdk.pb_8328b2bef1af4d0941a97cc98e810c6c.o)_OB JC_CLASS _在FirebaseCrash(Sdk.pb_8328b2bef1af4d0941a97cc98e810c6c.o)$ _ FCRMSGAndroidDevice _OBJC_CLASS _在FirebaseCrash(Sdk.pb_8328b2bef1af4d0941a97cc98e810c6c.o)$ _ FCRMSGIOSDevice _OBJC_CLASS _ $ _在FirebaseCrash(Sdk.pb_8328b2bef1af4d0941a97cc98e810c6c.o)FCRMSGApplication _OBJC_CLASS _ $ _ FCRMSGAndroidApplication在FirebaseCrash(Sdk.pb_8328b2bef1af4d0941a97cc98e810c6c.o).. “_OBJC_CLASS _ $ _ GSDK_PBMutableArray”,从引用:在FirebaseCrash(FCRCrashDump_ee5f791af340383d1b426338c1150e39.o)objc级-REF “_OBJC_CLASS _ $ _ GSDK_PBRootObject”,从引用:_OBJC_CLASS _ $ _在FirebaseCrash(Sdk.pb_8328b2bef1af4d0941a97cc98e810c6c.o)FCRMSGSdkRoot “_OBJC_CLASS _ $ _ GTMLogBasicFormatter”,引用来自:在FirebaseCrash(FCRSystemLogger_6532fb37dc095ffa73463b57baf5fca7.o)objc级-REF “_OBJC_CLASS _ $ _ GTMLogNoFilter”,从引用:objc级-REF在FirebaseCrash(FCRSystemLogger_6532fb37dc095ffa73463b57baf5fca7.o) “_OBJC_CLASS _ $ _ GTMLogger”,从引用:objc级-REF中FirebaseCrash(F CRSystemLogger_6532fb37dc095ffa73463b57baf5fca7.o)objc级-REF在FirebaseCrash(uploader_089041b840f448492d858d7daf481e47.o) “_OBJC_METACLASS _ $ _ GSDK_PBGeneratedMessage”,从引用:_OBJC_METACLASS _ $ _ FCRMSGTimestamp在FirebaseCrash(Sdk.pb_8328b2bef1af4d0941a97cc98e810c6c.o)_OBJC_METACLASS _ $ _ FCRMSGCrashReport在FirebaseCrash(Sdk.pb_8328b2bef1af4d0941a97cc98e810c6c.o)OBJC_METACLASS $ _FCRMSGDevice在FirebaseCrash(Sdk.pb_8328b2bef1af4d0941a97cc98e810c6c.o)_OBJC_METACLASS _ $ _在FirebaseCrash(Sdk.pb_8328b2bef1af4d0941a97cc98e810c6c.o)FCRMSGAndroidDevice _OBJC_METACLASS _ $ _在FirebaseCrash(Sdk.pb_8328b2bef1af4d0941a97cc98e810c6c.o)FCRMSGIOSDevice _OBJC_METACLASS _ $ _ FCRMSGApplication在FirebaseCrash(Sdk.pb_8328b2bef1af4d0941a97cc98e810c6c.o)_OBJC_METACLASS _ $ _ FCRMSGAndroidApplication在FirebaseCrash(Sdk.pb_8328b2bef1af4d0941a97cc98e810c6c.o)...... “_OBJC_METACLASS _ $ _ GSDK_PBRootObject”,从引用:_OBJC_METACLASS _ $ _ FCRMSGSdkRoot在FirebaseCrash(Sdk.pb_8328b2bef1af4d0941a97c c98e810c6c.o)“_kFIRAppNameKey”,引自:___17 [FCRClient load] block_invoke在FirebaseCrash(FCRClient_482ceec6b5943edbfb1d1dff6beb18f6.o)“kFIRAppReadyToConfigureSDKNotification”中,引自:FirebaseCrash中的[FCRClient load](FCRClient_482ceec6b5943edbfb1d1dff6beb18f6.o)“kFIRLoggerCrash”,从参考: - 在FirebaseCrash(FCRBreakpadController_bc3acad0fa3a54a5c7c331f54af621b0.o)[FCRBreakpadController enableDebugger] - [FCRBreakpadController startWithConfiguration:]在FirebaseCrash(FCRBreakpadController_bc3acad0fa3a54a5c7c331f54af621b0.o) - [FCRBreakpadController createDirectory:]在FirebaseCrash(FCRBreakpadController_bc3acad0fa3a54a5c7c331f54af621b0.o)[FCRAnalytics messageDictionaryFromMessage:]在FirebaseCrash(FCRAnalytics_281d4dbe093b1d2a74ef0873d1ac6263.o) - [FCRClient startWithConfiguration:错误:]在FirebaseCrash(FCRClient_482ceec6b5943edbfb1d1dff6beb18f6.o) - [FCRCrashDump crashInfoFromSystemMetadata:]在FirebaseCrash(FCRCrashDump_ee5f791af340383d1b426338c1150e39.o) 49- [FCRBulkUploader uploadFileFromQueue:的onSuccess:] _ block_invoke在FirebaseCrash(FCRBulkUploader_af76d0815dcb863205f4ed96c30df68e . o)... ld:找不到架构x86_64 clang的符号:错误:链接器命令失败,退出代码为1(使用-v查看调用)

已设置框架搜索路径和库搜索路径如下
enter image description here

1 回答

  • 0

    尝试cocoapods经理: pod 'Firebase', '~> 3.9'

    它可以简单地修复你所有错误的依赖 .

    https://cocoapods.org/pods/Firebase

    或者检查readme.md文件:你必须添加所有这些库:

    “(〜> X)”下面表示SDK需要X中的所有框架 . 在包含SDK时,应确保包含X中的所有框架 . 分析FirebaseAnalytics.framework FirebaseCore.framework FirebaseInstanceID.framework GoogleInterchangeUtilities.framework GoogleSymbolUtilities.framework GoogleToolboxForMac.framework崩溃(〜> Analytics)FirebaseCrash.framework

相关问题