Markus Hintersteiner

Let's start with having this feature as opt-in.

@yogurtearl thanks for the suggestion! We've added it to our backlog. In the meantime you could utilize `Sentry.setTag("play-device-class", )` to manually supply this information.

@gent-ahmeti thanks for opening this up! We'll have a look into this. Could also share the version of Timber you're using?

@gent-ahmeti thank you! Could you also share some more details on how you adapted it for the usage with Coroutines? Timber itself utilizes `ThreadLocal` for tags which could cause troubles...

@gent-ahmeti awesome, thanks for sharing! This should give us enough context to reproduce the issue. I'll keep you posted about any updates!

Long overdue update: We're currently blocked by the internal ThreadLocal usage within Timber itself, as it's not exposing any APIs to provide ways to make the tag value coroutine-aware. Blocked...

@gent-ahmeti Could you share a few code snippets on how you're using `Timber.tag()` within your codebase? As [outlined here](https://github.com/JakeWharton/timber/issues/565#issuecomment-3150769627) `Timber.tag()` should be immediately followed by a `.log()` call, otherwise you...

Quick update: We published an alpha release for `sentry-java` ([7.15.0-alpha1](https://github.com/getsentry/sentry-java/releases/tag/7.15.0-alpha.1)) for testing purposes

> > Quick update: We published an alpha release for `sentry-java` ([7.15.0-alpha1](https://github.com/getsentry/sentry-java/releases/tag/7.15.0-alpha.1)) for testing purposes > > @markushi any details on usage/validation of this change? @bruno-garcia @bitsandfoxes We don't have...

Possible solutions: 1. ) Add an option to SentryOptions 2. ) Allow the customer to remove the Integration and re-add it during init with different settings