Stefan Jandl

With https://github.com/getsentry/sentry-unity/pull/451 we already have all we need. The integration-test builds an empty project and then adds Sentry and builds it again. We could use those?

@vaind yes, it's reproducible locally. I gave your suggestion a try but the outcome is the same.

Interesting idea! We've already been discussing adding more Unity-specific context data to the events and this might be a way forward. Thanks for your input.

hey @rthery, thanks for bringing this up. I can see you point. let me get back to you.

So this is about Java? We have to check for `AttachThreads` when setting the Android options during the build. It should be the default behavior. Let me take a look.

Do you have an idea of what API you'd need to be made available?

Something like this should work as a workaround and we can add this to the docs? ```c# class CustomSentryBuildProcessor : IPreprocessBuildWithReport { public int callbackOrder => 0; public void OnPreprocessBuild(BuildReport...

We just need to be careful with the `callbackOrder` in case we want to use it ourselves at some point.

> during build time - the resulting config will also be used by the native initialization. Unfortunately, the Options Configuration via the script in the screenshot won't affect the native...

I stand corrected. That is a regression. Initially, we wanted to call it inside of `SentryInitialization`. So it would work but this is not intentional behaviour.