Open DavidMarquezF opened 3 days ago
Obviously we don't have anything to do with how Google's Firebase Crashlytics operates, so there isn't much we can do there. But Java.Lang.Throwable.FromException
is ours and maybe it can be improved to provide a better translation of the stack trace.
Will transfer to the dotnet/android
repository for investigation.
Oh, right, it moved to a different GitHub organization and we can no longer transfer issues to it. 😢
@jpobst should i close here and open it there?
This should already be fixed here since I faced this issue before and "complained" at @jonpryor on discord about it 😄 https://github.com/dotnet/android/pull/8185
Android framework version
net8.0-android
Affected platform version
2022 17.11.4, NET 8
Description
Since the https://github.com/xamarin/GooglePlayServicesComponents/ repository is now considered deprecated I'm reopening https://github.com/xamarin/GooglePlayServicesComponents/issues/423 here.
The main issue is that Crashlytics uses
Java.Lang.Throwable
. To convert our exceptions to this type we can useJava.Lang.Throwable.FromException
. However, the resulting crash logs are pretty hard to read and use compared to when we were using AppCenter (to be deprecated in 2025). On top of that inner exceptions are not even displayed, so for some issues it's impossible to know what actually happened.Given the deprecation of AppCenter and Firebase being the logical alternative (other than sentry), it feels like a big downgrade to not be able to get proper readable logs.
Steps to Reproduce
Did you find any workaround?
You can try to prepare the logs a little bit better yourself by using regex (as seen in this gist). However this is only for managed exceptions. We don't have any way currently to act on unmanaged exceptions.
Relevant log output