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

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 ?

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 :)

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

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

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.

Thank you for your answer.
Actually, not be able to pass a parameter for the priority is not a problem, because I can customize the message with my own prefix (E/ , W/ , I/).

So yes, I just think a good behavior could be stopping to log the superfluous "D/FirebaseCrashlytics"

For the moment, I have this on the firebase console (with the last implementation)

And if I download the .log file from firebase :

Hi @lionel-dangelo We have implemented removing the uperfluous log and it will be released in beta02. Here's the pull request #1247.

Thanks so much for the feedback.

I am closing this issue for now. I'd recommend checking out our releae notes to see when a PR makes it into an official release. Any new features/breaking changes/bug fixes should be detailed there :)