Menu
My iOS app is running firebase reports since several weeks.
I added crashlytics 2 days ago by following the official steps:
https://firebase.google.com/docs/crashlytics/get-started?authuser=0
in fact, It seems all I had to do was to install these pods:
pod 'Fabric', '~> 1.7.2'
pod 'Crashlytics', '~> 3.9.3'
I also added "DWARF with dSYM File" for the debug information format on both debug and release build settings
Now when I start the app I can see in the log :
[Crashlytics] Version 3.9.3 (128)
Then I forced a crash from an app launched manually (not with the debugger), and I can see the following in the logs after I restart the app from xcode:
[Crashlytics:Crash:Reports] Packaged report with id '9aeb11f6423b4f11b95a0f3263fc7510' for submission
nothing else regarding crashlytics
my question : Why I can't see any data in the firebase crashlytics reports?
943
If you can find the missing dSYM there, you can upload it again to fix the issue. Sometime, Apple Connect returns some wrong UUIDs, it means the user crashes on a binary has a missing UUID but Firebase Crashlytics received the dSYM of the wrong UUID so they cannot link together and cause the issue.
Firebase Crashlytics, a real time crash reporting tool, helps you prioritize and fix your most pervasive crashes based on the impact on real users. Crashlytics also easily integrates into your Android, iOS, macOS, tvOS, and watchOS apps.
To give yourself more context for the events leading up to a crash, you can add custom Crashlytics logs to your app. Crashlytics associates the logs with your crash data and displays them in the Crashlytics page of the Firebase console, under the Logs tab.
By default, Firebase Crashlytics automatically collects crash reports for all your app's users. To give users more control over the data they send, you can enable opt-in reporting instead. To do this, you have to disable automatic collection and initialize Crashlytics only for opt-in users.
You can associate arbitrary key/value pairs with your crash reports, then use the custom keys to search and filter crash reports in the Firebase console. In the Crashlytics dashboard, you can search for issues that match a custom key.
Crash reports stopped appearing in crashlytics console mid-November with both old and new version of the app, with some of the newer versions updated to 17+ version of the Google Crashlytics SDK. Debugging the app locally with logcat enabled shows Crashlytics initializing but not the usual logcat entries seen when a crash report is being sent.
For those who are still having problems. Check if you still have pod 'Firebase/Crash' in your podfile.
My problem was fixed when I removed the old Firebase Crash Reporting.
143
You're using the right pods for Crashlytics in Firebase - you need both the Fabric and Crashlytics pods.
Crashes should appear in the Firebase dashboard with the instructions you went through in https://firebase.google.com/docs/crashlytics/get-started?authuser=0. Make sure you also have Firebase Core in your project by following the "Before you begin" steps.
It's possible that your dSYM is missing, which is needed to symbolicate your crashes. Take a look at https://firebase.google.com/docs/crashlytics/find-missing-dsym?authuser=0 for instructions on how to upload your dSYM and then try out another test crash.
Also, check out my comment in the other answer for clarifications around Crashlytics in Firebase vs Fabric.
21
FYI I had a similar experience, except that my errors started showing up within a few hours. Here are the two sets of instructions I followed, the second of which is actually necessary even though it isn't included in "get started":
The steps I followed, in case you want to go down the list and make sure you didn't miss anything:
Instead of Crashlytics.sharedInstance().crash(), call:
let x: Int? = nil
let y = 5 + x!
Run, stop, click, tap button, crash. Restart.
I'd advise looking at system logs, but it looks like you've already done that. I hope some part of this gives you an idea that helps.
28
Check run script only when installing
30
I tried the same yesterday, where I crashed the app multiple times. Both with Crashlytics.sharedInstance().crash() and
let x: Int? = nil
let y = 5 + x!
with no results in the dashboard.
Today I tried implement Firebase Crashlytics in another app. But this time I run it on a device instead of in the simulator. And within 5 min. I got data in the dashboard.
So my suggestion is: Try run it on a real device instead of in the simulator.
36
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
