You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I might be missing something, but I can't find a way to implement a CrashReportingTree like in the example that implements TaggedTree instead of Tree.
As a consequence of this, logs sent to Crashlytics don't have the context of the tag associated to them, which make them pretty useless.
It would be great if the tagging functionality implemented in DebugTree was abstracted out so that other subclasses could reuse it, or if the implementation of the Tree methods weren't marked as final so that they could be overridden to forward logs to Crashlytics instead (or anything else).
The text was updated successfully, but these errors were encountered:
I might be missing something, but I can't find a way to implement a
CrashReportingTree
like in the example that implementsTaggedTree
instead ofTree
.As a consequence of this, logs sent to Crashlytics don't have the context of the
tag
associated to them, which make them pretty useless.It would be great if the tagging functionality implemented in
DebugTree
was abstracted out so that other subclasses could reuse it, or if the implementation of theTree
methods weren't marked asfinal
so that they could be overridden to forward logs to Crashlytics instead (or anything else).The text was updated successfully, but these errors were encountered: