Firebase Crashlytics Not Showing Crash Report in Console Dashboard Swift

Firebase Crashlytics doesn't show changes in Dashboard/Console iOS app

My guess is that you're simulating a crash with the debugger still attached, so Crashlytics can't catch it, hence why you have nothing in your dashboard.

To properly test your implementation locally, follow these steps:

  • Click Build and then run the current scheme (the play button) in Xcode to build your app on a device or simulator.
  • Click Stop running the scheme or action (the stop button) in Xcode to close the initial instance of your app. This initial instance
    includes a debugger that interferes with Crashlytics.
  • Open your app again from the simulator or device.
  • Force a crash in your app.
  • Open your app once more to let the Crashlytics API report the crash. Your crash should show up in the Firebase console within 5
    minutes

Source: https://firebase.google.com/docs/crashlytics/force-a-crash

iOS Firebase Crashlytics not showing up crashes in Dashboard

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.

Configuring Crashlytics Without Using CocoaPods Not Getting Crash Reports

These configurations are not directly related to Crashlytics' crash report operation. These are used to send desymbollers to Firebase. So Firebase can desymbol your crash info and provide you a readable crash report. So, I am not sure that a failure in these configurations can cause your problem. As I know, if you have a failure in these steps; After your app crash, you need to see "Missing dsymbols" error on Firebase Crashlytics panel

If you cannot see your crash report, you need to check steps to integrate crashlytics properly. And maybe enable Firebase debug mode and check logs.

By the way, Crashlytics' first integration steps may be annoying. You may need to read and apply these steps carefully. Especially test crash step.

iOS Crashlytics not logged in firebase dashboard

I had a very silly problem.I solved my problem. After you build with Xcode, you have to stop xcode and open the app manually.



Related Topics



Leave a reply



Submit