Markus Hintersteiner

Let's check if there are any breaking API changes due to the mentioned refactorings.

Let's be aware if the sync happens on a background thread, the data won't be available immediately on the NDK side. E.g. when next line in code performs JNI call.

Let's talk about this in the next sentry-native sync.

Let's check the top-level attributes in the data bag: If it's only primitives sync the breadcrumbs directly, otherwise offload to a background thread.

Let's check if we can get notified if the refresh-rate changes. We could fallback to the last known refresh-rate and simply count the number of expected frames.

If the tunnel option is set, the endpoint URL would be set to `tunnel` instead of the parsed DSN.

Hey @vanshg, thanks for reaching out! I guess expanding `SentryTraced` with a hub argument should be easy enough to cover your use case ```` public fun SentryTraced( tag: String, modifier:...

On a second thought, https://developer.android.com/jetpack/compose/compositionlocal would be a more "Compose" way of doing this. We even do that right now ([see source](https://github.com/getsentry/sentry-java/blob/main/sentry-compose/src/androidMain/kotlin/io/sentry/compose/SentryComposeTracing.kt#L34-L62)) we would just need to expose the APIs,...

As of now there's nothing stopping an app developer of integrating the Play Integrity API themselves and reporting the outcome via e.g. `Sentry.setTag()`. Let's keep this topic in mind, but...

Docs around this topic: https://docs.sentry.io/platforms/apple/performance/instrumentation/automatic-instrumentation/#prewarmed-app-start-tracing