Stefan Jandl

This has also been brought up through the Unity SDK: https://discord.com/channels/621778831602221064/621783582628642822/971159190166962216

Unity is on `Cocoa v7.23.0` right now and does not have this issue. Events reported through the Cocoa SDK show up as `sentry.cocoa.unity`.

I stand corrected: It's made its way into the Unity SDK as well: https://github.com/getsentry/sentry-unity/issues/950

We made it work without the need for a static lib.

Does scope.Platform qualify? https://github.com/getsentry/sentry-dotnet/issues/1590

> Maybe drop the "unity." prefix? Also, I've noticed the spans are missing names - what's the best practice in other SDKs? > > https://sentry.io/organizations/sentry-sdks/performance/sentry-unity:4e44bacb819a4509ac4bb20b2c53d154/?project=5439417&query=transaction.duration%3A%3C15m&statsPeriod=30d&transaction=unity.runtime.startup&unselectedSeries=p100%28%29 > > Thanks for pointing...

We're off the tagged version. - Don't merge.

This needs a bit of investigation to see if it's an issue on all platforms so that we might raise an issue with Unity. A nice repro would be to...

The `SentryWindow` would not get notified about a change to the player settings. But we could read them during pre-build and set it accordingly?

> Im seeing this still happen on 0.22.2 where it produces an error. I'm reasonably sure that this is not coming from `0.22.2`. The error message from your logs is...