| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Require an explicit Android option before forwarding Logcat calls as Sentry Logs. Support Java and manifest configuration while keeping breadcrumbs and Android Log calls unchanged. Co-Authored-By: Claude <noreply@anthropic.com>
|
Sorry, something went wrong.
📲 Install BuildsAndroid
|
Sorry, something went wrong.
Performance metrics 🚀
|
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM 👍
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
PR Stack (Logs and Metrics Enable Flags)
📜 Description
Adds SentryAndroidOptions.logcatLogsEnabled, defaulting to false, and the io.sentry.logcat.logs.enabled Android manifest key.
SentryLogcatAdapter now requires both this local opt-in and the existing aggregate core Logs flag before forwarding Logcat calls as Sentry Logs. The local check runs before throwable and message processing. Breadcrumb creation and the original Android Log invocation remain unchanged.
💡 Motivation and Context
Automatic Logcat instrumentation needs an explicit local opt-in before the aggregate core Logs flag can be removed. This prevents instrumented Android applications from unexpectedly forwarding Logcat output when core Logs capture becomes available without a global enable flag.
💚 How did you test it?
📝 Checklist
🔮 Next steps
Add the Spring Boot Logback opt-in before removing the aggregate core Logs flag.