Force FirebaseCrashlytics print logs to console

[bolds07]

What feature would you like to see?

I would like messages logged with FirebaseCrashlytics.getInstance().log("message"); and FirebaseCrashlytics.getInstance().recordException(new RuntimeException("exception"));

How would you use it?

The most important objective of loggin (not to say the only) is to identify and debug errors... Crashlytics is the best library I know for that, but in the current state the lib makes unnecessarily difficult to debug in development environment.

but as current state of firebase crashlytics it is impossible to do this in development environment.

Prior to google buy Crashlytics it was possible using the fabric api. But now seems these methods were removed.

The whole problem is, if I'm in the development environment and want to follow the code execution (by watching the log messages) Crashlytics wont show them... I need to intentionally cause an crash, then wait a time for it be uploaded to dashboard them start hunting for the registers among maybe thousands of others...

All other firebase libraries allow us to enable debug features which will print thousands of messages straight to console, but ironically the library made for debug doesn't allow it...

it is time to rethink this guys

[google-oss-bot]

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

[argzdev]

Hi @bolds07, apologies for the late response. This feature actually do exists. You may check out this link, which shows you how to create customized reports, including logging non-fatal exceptions. With that said, since this already exists, I'll be closing the case. Thanks.

[bolds07]

you took 2 months to read the issue and still you didnt read it right... IM SAYING PRINT THE LOG MESSAGES TO THE LOGCAT OR ANDROID STUDIO CONSOLE

IM NOT TALKING ABOUT PRINT IT INTO A ONLINE DASHBOARD WHICH ISNT REAL TIME AND WHICH TAKES A LOT OF EFFORT FOR ANYONE TO FIND THE DESIRED LOG

[argzdev]

Hi @bolds07, thank you for further explaining this, now I understand your pain point more and this is a reasonable request. Apologies for the misunderstanding. I've only read the "What features would you like to see", and automatically assumed this was the feature that already existed. This is a lacking on my part, I apologize. I'll reopen the issue now.

[mrichards]

Hi @bolds07, thanks for the feature request. You are correct that Fabric Crashlytics used to echo calls to log to LogCat by default. That behavior was removed due to repeated customer concerns about spamming LogCat. We can see the use of being able to toggle this behavior on or off for debugging purposes, so we'll consider adding it as a feature in a future release.

[prilaga]

Awesome approach - buy a service and make it worse. Thanks to holy java reflection that makes all the things that this team can't.

[fred-bowker]

I think a feature where when developing locally, firebase will log out to logcat makes a lot of sense, I can't see why customers would ask for this to be removed for spamming LogCat, surely if the app is crashing that much to be causing an issue in logcat, then the customer would want to fix that.

It would be really useful if this was implemented, in development you could then see any crashes in real time without having to wait for the crash to be reflected in Crashlytics