search

Q42 / Template.Android

MIT License
7 stars 0 forks source link

Crashlytics groups all non-fatal errors #57

Open ninovanhooff opened 9 months ago

ninovanhooff commented 9 months ago

The reason for this is that the stacktrace looks similar: the method that logs the exception is always our crashlogger class

https://stackoverflow.com/questions/47654410/how-to-effectively-group-non-fatal-exceptions-in-crashlytics-fabrics

I will implement the suggested workaround: https://stackoverflow.com/a/59779764

ninovanhooff commented 6 months ago

Created a bug report here: https://github.com/AAkira/Napier/issues/124

ninovanhooff commented 5 months ago

@Frank1234 no response to my report, while I consider this a severe issue. Wondering whether we should use Kermit instead. Did you consider Kermit? Why did you choose Napier?

Frank1234 commented 4 months ago

Do we have this in other projects? Also not in WIDM I think?

I choose it because Kermit is harder to setup and Napier is almost the same in usage our old logger: Tolbaaken.