Menu
Firebase crashlytics console displays "loading" after a click on the "Enable Crashlytics" button.
It displays the spinner. It has been like this for several minutes.
861
Open your app from the home screen of your test device or simulator. In your app, press the "Test Crash" button that you added using the code above. After your app crashes, run it again from Xcode so that your app can send the crash report to Firebase.
To mark a cluster as closed, click the three dots on the far right of the row that appear when hovering over the row, then click "close cluster."
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.
Keeping an eye out for issues that affect your app’s stability is crucial, but we also know that you can’t spend your entire day staring at the Firebase Crashlytics console. From the beginning, Crashlytics has given developers the ability to turn on stability alerts so they can be notified when issues increase in impact and severity.
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.
First, make sure that you've followed all the instructions here to get the Crashlytics SDK set up. Then, force a crash to test your implementation. This is required to get past the onboarding screen that you're seeing at the moment.
If that doesn't work, try enabling debug logging and going through the build, run, crash, and relaunch process again, and paste any Crashlytics or Firebase-related logs into your original question.
83
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
