Using custom logger in Android SDK #2925
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
BartoszLitwiniuk
requested review from
rick-bt and
peter-shao
as code owners
|
Should be merged after https://github.com/backtrace-labs/backtrace-android/pull/147/files |
melekr
approved these changes
Sep 4, 2024
konraddysput
approved these changes
Sep 4, 2024
rick-bt
approved these changes
Sep 4, 2024
|
Already merged. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Added example how to replace default BacktraceLogger used for logging internal SDK information by custom implementation.
Motivation and Context
It's adding example how to use this feature for clients. Should be merged after merging PR which introducing this feature backtrace-labs/backtrace-android#147.
Types of Changes