Stefan Jandl

Hey @ernesernesto unfortunately, no. But it's not forgotten nor dropped.

I can finally reproduce this locally! Thank you so much for the repro @ernesernesto!

> Is this problem solved now？I reappear in this version 1.5.2 @bitsandfoxes Are you referring to a different issue than the [known limitation](https://docs.sentry.io/platforms/unity/configuration/il2cpp/?original_referrer=https%3A%2F%2Fwww.google.com%2F#known-limitations) related to button click events?

Thanks for providing the repro @dingleqiang. Are you on Unity `2021.3.` as well?

A thousand apologies. I missed the notification on this one. I'll update our docs to properly reflect the current limitations. But to summarize it here: Events going through the logger...

`SentrySdk.CaptureException` works and events captured through this should have correct stacktraces and line numbers.

Thanks for raising this issue! Is this something that broke with an update of the SDK? Can you confirm that it previously worked?

These are options set for the [Sentry Android Gradle Plugin](https://github.com/getsentry/sentry-android-gradle-plugin) which the Unity SDK does not rely on.

Fixed by #1626

Looking through the logs this seems unrelated to the scope-observer fix. And since it's happening on Android 10 and 11 it also seems unrelated to the issue we see on...