Markus Hintersteiner
Markus Hintersteiner
We could by default init the native SDK off the main thread, avoiding the slow `System.loadLibrary()` calls on the main thread. Maybe it's worth adding a boolean flag to force-init...
This has been fixed with https://github.com/getsentry/sentry-java/pull/3670
In the meantime this could be solved using `beforeSendTransaction`.
@lbloder as [discussed here](https://github.com/getsentry/team-sdks/issues/95#issuecomment-2324425445), let's remove sending it as `event.extra`.
Let's use the protocol object, just like we do for the `beforeSendTransaction()` callback. Let's ensure we also report the dropped spans (via client reports).
Let's investigate first: * If/how we can instrument the different work schedulers * How the `queues` module works under the hood and if the data model would the mobile use...
Since sentry's concept of queues doesn't match WorkManager very well, we could have breadcrumbs and Events (e.g. for failed jobs) as well.
Hey @JohannesPtaszyk, thanks for reaching out. Just to better understand your use-case: How are you replacing the placeholders in your urls. Are you using a custom interceptor for this?
In the first iteration, let's roll with sending a custom event. At a later point we could think of doing the analysis right after an OOM happens (if possible).
Let's deprecate in 7.x and remove it in the upcoming 8.x release