Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crashlytics groups all non-fatal errors #57

Open
ninovanhooff opened this issue Feb 23, 2024 · 3 comments
Open

Crashlytics groups all non-fatal errors #57

ninovanhooff opened this issue Feb 23, 2024 · 3 comments

Comments

@ninovanhooff
Copy link
Collaborator

ninovanhooff commented Feb 23, 2024

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
Copy link
Collaborator Author

ninovanhooff commented May 17, 2024

Created a bug report here: AAkira/Napier#124

@ninovanhooff
Copy link
Collaborator Author

ninovanhooff commented Jul 12, 2024

@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
Copy link
Collaborator

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants