Firebase Crashlytics“加载问题时出错”和上载符号脚本错误-使用XCode的iOS应用 [英] Firebase Crashlytics 'Error loading your issues' and upload-symbols script error - iOS App using XCode

问题描述

我最近注意到我在Firebase Crashlytics中的所有崩溃报告都没有被清除，它们都返回了编译器错误和内存位置（例如< compiler-generated>-行4331771636 ， EXC_BREAKPOINT 0x0000000102afd6f4 ），而不是函数名和行号。我意识到这是因为Fabric已关闭（2020年5月4日），所以我开始过渡到Firebase Crashlytics。

I recently noticed all of my crash reports in Firebase Crashlytics were not being deobfuscated, they were all returning compiler errors and memory locations (eg <compiler-generated> - Line 4331771636, EXC_BREAKPOINT 0x0000000102afd6f4), rather than function names and line numbers. I realised it's because Fabric has been shutdown (4th May 2020), so I began the transition to Firebase Crashlytics.

我更改了pod文件并添加了 Firebase / Crashlytics 窗格，并按照这里。

I changed my pod file and added the Firebase/Crashlytics pod, and followed the transition instructions located here.

我已将以下代码放在我的 Run脚本下构建阶段在Xcode中：

I've put the following code in my Run script under Build Phases in Xcode:

"${PODS_ROOT}/FirebaseCrashlytics/run"
"${PODS_ROOT}/FirebaseCrashlytics/upload-symbols" -gsp "${PROJECT_DIR}/GoogleService-Info.plist" -p ios "${DWARF_DSYM_FOLDER_PATH}/${DWARF_DSYM_FILE_NAME}"

构建项目时，我从 upload-symbols ：

Fetching upload-symbols settings...
[31merror: Could not fetch upload-symbols settings: Could not connect to the server.[0m
Command PhaseScriptExecution failed with a nonzero exit code

如果我手动运行 upup-symbols 脚本在终端中，我收到相同的错误错误：无法获取上载符号设置：无法连接到服务器。

If I manually run the upload-symbols script in terminal, I get the same error error: Could not fetch upload-symbols settings: Could not connect to the server.

我还注意到，在Firebase的Crashlytics仪表板上，我丢失了所有以前的崩溃数据，并收到消息加载您的错误问题。

I also noticed that on the Crashlytics dashboard in Firebase, I had lost all my previous crash data and was receiving the message Error loading your issues.

如何解决错误并使Crashlytics像以前一样工作？

How can I fix the errors and get Crashlytics working like before?

推荐答案

解决方案是使用 fatalError（）强制应用崩溃。显然，在Firebase Crashlytics后端完成新SDK的注册是否需要这样做。

The solution was to force a crash in my app using fatalError(). It is not obvious that this is required to finalise the registration of the new SDK with the Firebase Crashlytics backend.

完成此操作后，我所有的历史崩溃数据都像以前一样可用，并且 upload-symbols 成功完成。

After doing this, all my historical crash data is available like before, and upload-symbols completes successfully.

这篇关于Firebase Crashlytics“加载问题时出错”和上载符号脚本错误-使用XCode的iOS应用的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！