Manoel Aranda Neto
Manoel Aranda Neto
@jadbaz this feature isn't supported yet, I'd prefer to not share a hacky solution with flawns, please upvote the issue, and let's see if we can get prioritized.
It'd benefit when you have an unstable connection, or no connection at all. Events are always sent on restart anyway. Also when you never close/kill the app very often, the...
@romtsn The Java SDK already has such annotations https://github.com/getsentry/sentry-java/blob/main/sentry-spring/src/main/java/io/sentry/spring/tracing/SentryTransaction.java In case the target and retention match, we could e.g. move it to the core package.
Investigate the ExecutorService -> https://github.com/getsentry/sentry-java/issues/2115#issuecomment-1164459003
> If we decide to throw away the event, we should ensure this information ends up in [client reports](https://develop.sentry.dev/sdk/client-reports/). Actually, it's the opposite, by swallowing the exception during eg `beforeSend`,...
@Nohus we intend to work on it and it's in our backlog, but it's not prioritized yet.
@adinauer Should we move this issue to In progress and add to v6? or the hints improvements won't automatically fix this? Thanks.
Related PR https://github.com/getsentry/sentry-android-gradle-plugin/pull/317
Issue that will likely be addressed as well -> https://github.com/getsentry/sentry-java/issues/2037
We don't think its a breaking change since this public API does not change, the chart timeline does not change, but only the hierarchical view of the spans.