Firebase Crash Reporting A Few Problems

I install Firebase Crash Reporting in my iOS app. I imported the necessary json files and installed the shell script. However, when I press the start button on the simulator, I get 11 errors that all say the same. Here are two of them:

warning: dump_syms: /var/folders/5l/20by_c_57fb7jhv3jh72jw9m0000gn/T/com.google.FirebaseCrashReporter.TAlixfZc/**App Name**.dSYM/Contents/Resources/DWARF/**App Name**: in compilation unit '/Users/mikelehen/firebase/firebase-client-objc/Firebase/Firebase/Utilities/FUtilities.m' (offset 0x28a2e): ` warning: dump_syms: /var/folders/5l/20by_c_57fb7jhv3jh72jw9m0000gn/T/com.google.FirebaseCrashReporter.TAlixfZc/**App name**.dSYM/Contents/Resources/DWARF/**App Name**: the DIE at offset 0x28fc1 has a DW_AT_abstract_origin attribute referring to the die at offset 0x2940f, which either was not marked as an inline, or comes later in the file ` 

When I try to run it on my iPhone, I get only four problems.

Also, my name is not mikelehen, which for some reason is in one of the problems.

After following the instructions on the Firebase website to simulate a crash, I never get a log of a downloadable crash.

Any idea what I'm doing wrong here?

Edit: Here is the script that is in my build phases:

 JSON_FILE="../**App Name**/ServiceAccount.json" GOOGLE_APP_ID=1:**App ID** defaults write com.google.SymbolUpload version -integer 1 JSON=$(cat "${JSON_FILE}") /usr/bin/plutil -replace "app_${GOOGLE_APP_ID//:/_}" -json "${JSON}" "$HOME/Library/Preferences/com.google.SymbolUpload.plist" "${PODS_ROOT}"/FirebaseCrash/upload-sym 
+7
ios firebase firebase-crash-reporting
source share
5 answers

Try:

  • Build Phases -> Run Script
  • Click Run script only when installing
+8
source share

These warnings are not harmful for the most part. The dump_syms utility that ships with Cocoapod is not fully developed, so it reports errors using the file names of the person who compiled the latter (in this case mikelehen). We are actively exploring dump_syms alternatives as warnings distract.

+3
source share

As mentioned by Robert, warnings are harmless. Here are some suggestions that can help you if you have problems downloading:

1) Make sure that the debugger is not connected when a failure occurs. It will catch the exception, and nothing is reported about it. So, compile your program, click β€œStop” in the debugger, launch the application manually (either in the simulator or in the device), you can start the crash and then restart the application (without crash, so that the error can report).

2) You should see a log message stating that Firebase Crash Reporting has been initialized. If this is not enough, make sure you enable the Firebase / Crash module and call [FIRApp configure] ;.

3) Within 15 seconds you should see another message stating that the report was sent successfully. Be sure to wait at least 15 seconds. Reports are downloaded after a delay to avoid interfering with the application launch.

4) After the report has been downloaded, there is a delay of up to 20 minutes before the data appears in the web console.

5) If you are not using cocoapods, be sure to add the ObjC linker flag to other linker settings in your target build settings.

0
source share

You can follow this screenshot. You can customize Crash Reporting. You get the result: set up a crash report

http://i.stack.imgur.com/NPSBm.png

0
source share

The generated dump_syms warnings are not harmful and are generated when loading symbol files. Therefore, if you want to avoid warnings each time you create, you can create two goals; debugging and release. Then simply turn off the option β€œRun script only on installation" for Debug and enable it for release. This will load the symbol files.

0
source share