Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

iOS Firebase Crashlytics not showing up crashes in Dashboard

I implemented Firebase Crashlytics in my iOS app. I followed all the steps in firebase documentation. I already ran crashlytics without the debugger by closing the app first and then re run the app so that crash reports can be sent. I even get this message

Crash upload submission succesful

I even added the Run script and set variable to "DWARF with DSYM"

"${PODS_ROOT}/Fabric/run"

I ready somewhere that if DSYM aren't uploaded you won't see your crashes even if they are uploaded successfully. So I went into my pods/Fabric/ and click on "run" CLI. It clearly says DSYM not uploaded because GoogleServiceInfo.plist wasn't found. Although it's there and yes it's included in my target as well as in my bundle.

enter image description here

Here is the screenshot. I have tried all possible steps to include GoogleService-Info.plist but still when I run manually it says this.

enter image description here

Any another thing that I can try ?

like image 845
Moaz Khan Avatar asked Dec 22 '17 07:12

Moaz Khan


People also ask

Where are crashes in Firebase console?

Once you have Crashlytics up and running in your app, you can navigate to Crashlytics in your Firebase Console underneath 'Quality' and start reviewing the reports as they come in. If this page still tells you to setup, build or run your app then you have not correctly setup Crashlytics in your app (see Usage).

How does Firebase Crashlytics work in IOS?

Firebase Crashlytics is a lightweight, realtime crash reporter that helps you track, prioritize, and fix stability issues that erode your app quality. Crashlytics saves you troubleshooting time by intelligently grouping crashes and highlighting the circumstances that lead up to them.


Video Answer


3 Answers

Try this:

  1. Run your app from Xcode to install it on the simulator or your device
  2. Press the Stop button in Xcode to quit it
  3. Launch your app from the home screen to run it without the debugger
  4. Press the “Crash” button to trigger the crash
  5. Run the app again from Xcode so it can deliver the recorded crash to Crashlytics
  6. Within a few minutes, you should see the crash appear on your Firebase Crashlytics Console.

For reference:

Integrating Firebase and Crashlytics in iOS 

like image 196
Piero Sifuentes Avatar answered Oct 17 '22 16:10

Piero Sifuentes


I have tried serval things but below steps are worked for me

  1. Put FirebaseApp.configure() to first line of didFinishLaunchingWithOptions
  2. If you have both Firebase/Crashlytics and Crashlytics. Removed Crashlytics from pods and update it
  3. Check in Build Phases Run Script if you have entry fot "${PODS_ROOT}/FirebaseCrashlytics/run".
  4. If you're running app in debug mode make sure you have added -FIRDebugEnabled in Project's test scheme.
  5. Run the App From Home Screen(Don't run it from Xcode) and crash it on any button's Action.(you will find the crash in Firebase Console with in 5-10 mins)
like image 11
Sahil Avatar answered Oct 17 '22 15:10

Sahil


To someone still struggling with the issue here is what resolved the issue for me.

  1. I deleted the GoogleService-Info.plist and added it again.

  2. I tried the crash on my welcome screen rather than in one of the screens of my tab bar controller as I believe from there it's unable to find GoogleServiceInfo.plist file so it worked.

like image 6
Moaz Khan Avatar answered Oct 17 '22 15:10

Moaz Khan