CODEWITHSUNDEEP
androidfirebasecrashlyticsfirebase-crash-reportingcrashlytics-android
Rafael Lima
Rafael Lima

Reputation: 3535

Where does Crashlytics.log(""); go?

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?

Upvotes: 8

Views: 9257

Answers (4)

Rafael Lima
Rafael Lima

Reputation: 3535

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

Upvotes: 0

Bali
Bali

Reputation: 759

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

Firebase Crashlytics Dashboard

One more thing if you want to log exceptions there is another method for it Crashlytics.logException(exception)

Upvotes: 5

Jake Lee
Jake Lee

Reputation: 7989

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.

Upvotes: 6

akaMahesh
akaMahesh

Reputation: 381

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)

Upvotes: -2

Related Questions