As firebase started supporting Crashlytics the Firebase crash reporting option is no longer available. Is there any way to see the Firebase crash reporting for the existing app which already using Firebase crash reporting
Mike from Firebase here. If you don't see the screen that Yogesh mentioned, from the Crashlytics dashboard, click on your app under Crashlytics and you should see both Crashlytics and Crash Reporting mentioned in order to switch between the dashboards.
If your project using crash reporting, then it is showing like this.
or like this
Related
I'm using Firebase Crashlytics to report crashes. I'm using a game framework that handles logging for me and when running on Android, it logs to LogCat. I want to be able to include the LogCat logs with the crash report in Crashlytics. Is this possible?
I found this Library that could help (https://github.com/Ereza/LogcatReporter), but I'm not sure how well supported it is.
I know I can log like this:
FirebaseCrashlytics crashlytics = FirebaseCrashlytics.getInstance();
crashlytics.log("my message");
crashlytics.log("E/TAG: my message");
But I would prefer for the framework I'm using to handle the logging.
Any way to include those LogCat logs? Does Firebase have a built in supported way?
I suppose there is no feature to save logs into Firebase Crashlytics, but I found an interesting solution for saving logs into Firebase Realtime Database.
Anyone know what this error is about? It shows up each time I open an event in Firebase Analytics Console.
The only thing I can think of that has changed recently is that my user's role has changed from Viewer to Editor.
Having recently switched from Fabric to Firebase for analytics and crash reporting (Android), you can see why it does not inspire a lot of confidence when this pops up all the time.
Thanks in advance!
--- EDIT ---
I have found some issues from within the console:
I'm trying to set up my app with firebase+crashlytics for having a better error dashboard.
All the firebase stuff is already working and I'm able to access the features
I tested crashlytics with:
Crashlytics.getInstance().crash(); // Force a crash
and i'm able to see the stack trace on my dashboard (inside firebase)
but I'm trying to log non-fatal messages like:
Crashlytics.log("test");
And it doesn't appear anywhere
I followed the whole instructions at:
https://firebase.google.com/docs/crashlytics/customize-crash-reports
Still doesn't find any dashboard with the "test" messages
Where does it go? what am I missing?
Sending non-debug errors (e.g. your test message) logs to Crashlytics locally, but these exceptions are not uploaded until the app restarts.
As the documentation states:
Crashlytics batches logged exceptions together and sends them the next time the app launches.
This is presumably due to the primary Crashlytics functionality (reporting crashes) working in the same way, and non-fatal errors being a secondary concern using the same code flow.
Whilst this is unfortunate, there are many third party log-collating services that can handle the non-fatal errors.
Note: I'm aware you've received an answer in the comments from Crashlytics, I'm providing a more comprehensive answer for future visitors.
It's an old question any way i wanted to share what happens to messages logged using Crashlytics.log(msg); These logs are not immediately shown to dashboard. Crashlytics stores all the logged messages logged using log(msg) method and uploads it to server when a new Crash or Exception occurs.
You can see these messages in Firebase console under logs section as shown in below image
One more thing if you want to log exceptions there is another method for it Crashlytics.logException(exception)
Crashlytics isn't made for develop logging/debug, it is made to cluster hundreds/thousands of logs from different users at runtime, this may cause delays between the time the log message are recorded and when you will really be able to see them at the dashboard making it unusable for development debug.
If you want to use Crashlytics to follow the code workflow and debug during development, you will need to use the trick in this answer.
https://stackoverflow.com/a/69340289/5679560
As mentioned in below link
https://support.crashlytics.com/knowledgebase/articles/120066-how-do-i-use-logging
You can see this crashes on Crashlytics dashboard if you look at the specific crash itself.
The recommended way to add custom logging to your app is:
Crashlytics.log(int priority, String tag, String msg)
As announced by Google, the Firebase Crash Reporting is joining forces with Fabric. Here's a link
The exact details of how is this going to happen are abstract. But for developers who were using Firebase Crash Reporting, does this mean that they have to create a new account on Fabric and integrate its SDK and remove the one from Firebase?
I know I could wait until Google does the actual implementation, but switching from one SDK to another is not the best approach, if anyone has any insight on this...
The following is the text from the Firebase console when looking at Crash Reporting for the first time without any existing data. There's no additional information available about how exactly it's going to work.
Fabric’s Crashlytics
In the future, Fabric’s Crashlytics will become our primary crash
reporter because it provides advanced tools for solving stability
issues. If you’d like to be an early adopter, you can get a head start
by using Crashlytics on Fabric’s platform.
Crash Reporting
If you prefer to monitor stability in Firebase, you still have access
to Firebase Crash Reporting, which equips you with the essential tools
you need to track and resolve crashes. Eventually, Firebase Crash
Reporting will be seamlessly upgraded to Crashlytics.
according to the Google groups discussion, they recommend ppl to use crashytics for now if they don't have any strong preferences.
https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/firebase-talk/_uUuJm0wui8/rHuWYKbABwAJ
Ian Barber
We're mainly trying to signal forward intent - the feature sets are slightly different so I appreciate you may prefer to use Firebase Crash on a new app, but for those with no standing inclination we're recommending they go with crashlytics.
I've kept myself from using Firebase Analytics and Crash Reports because there was no way of disabling Crash Reporting.
I've seen the answers on other questions but not offered a proper way of doing it.
I've read an interesting thing on Firebase blog: https://firebase.googleblog.com/2017/03/take-control-of-your-firebase-init-on.html
I wonder, could this be used do disable analytics and crash reporting?
I mean, heaving something like:
if (user.wantsAnalytics()){
FirebaseApp.initializeApp(this, builder.build());
}else{
//do nothing and no analytics or crash reports will be sent.
}
If firebase isn't initialized, would push messaging still work?