FirebaseCrashlytics log() method takes only a message without priority and tag

Why the only way to log something is FirebaseCrashlytics.getInstance().log(message) without tag and priority ? If we look the implementation, we see that this method calls the CrashlyticsCore method
public void log(String msg) { this.doLog(3, "FirebaseCrashlytics", msg); }

and this method sets always a the Debug priority (3) and the tag "FirebaseCrashlytics" which is not really readable in the firebase crash console.
Is this a bug ?

Thank you

[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.

[aguatno]

Hi @lionel-dangelo thanks for filling this issue. Crashlytic.log() has a similar method with same name, but different argument wherein you can set the tag and priority, see image below for reference.

Thank you for your answer, but I try to use the new implementation of FirebaseCrashlytics (without Fabric)
https://firebase.google.com/docs/crashlytics/get-started-new-sdk?platform=android
So I don't have the "Crashlytics" class anymore and the new class "FirebaseCrashlytics" exposes only log(String msg)
Maybe is there an other way with the new implementation ?

[aguatno]

Thanks for the clarification. It seems there should be another log() method with priority and tag as parameter, see here.

The Firebase Crashlytics SDK for Android is still a beta release so there are still a few issues that need to be addressed. I'll be tagging this issue as bug for now.

Thank you :)

[aguatno]

For now, you may try to log a message with tag using this syntax:

FirebaseCrashlytics.getInstance().log("E/TAG: my message");

You can read more here.

Yes it works, but like I said in my first message it's just not ideal because FirebaseCrashlytics.getInstance().log() calls the method log(msg) of CrashlyticsCore
public void log(String msg) { this.doLog(3, "FirebaseCrashlytics", msg); }
so alls my messages are prefixed by D/FirebaseCrashlytics
Example :
D/FirebaseCrashlytics I/SharedPrefsServiceImpl.kt:4)#<init>: SharedPrefsService initialization
D/FirebaseCrashlytics I/StorageServiceImpl.kt:2)#<init>: StorageService initialization
D/FirebaseCrashlytics I/ApiContextServiceImpl.kt:1)#l: Init authentication from prefs

I'm going to use the library like that and I'll wait for an improvement.
Thank you

[aguatno]

Issue is being tracked internally using bug#148943501. I'll keep you posted.

[aguatno]

Hi @lionel-dangelo I got feedback from our engineering team. It is intended behavior that priority and tag has been taken out in the Firebase Crashlytics SDK. We do log a priority and tag internally, but it's always "D/FirebaseCrashlytics,".

We would like to ask your feedback on what you think of either of these changes to the log method:

1. Stop logging the superfluous "D/FirebaseCrashlytics"
2. Allow users to configure that for display in their dashboard, without actually passing it through to logcat.

Thanks.