Ivan Dlugos

OK, so the stack traces for the embedded code coming from Unity `.jslib` are pretty limited but I don't think there's much we can do, they're just not there on...

As per a discord discussion: * this is rather important for the Windows standalone support so bumping to P1 * until the dotnet issue is resolved, implement a named mutex...

Updating impact, priority & status after the workaround has been implemented. The final solution is blocked by the dotnet issue.

The exception you see was and seemingly still is the only way we can indicate to `sentry-dotnet` SDK that the preconfigured screenshot attachment cannot be produced for the current event....

> Can we just skip the screenshot in this case and let it continue? that is what happens in the end, it **just** logs as an error: https://github.com/getsentry/sentry-dotnet/blob/94e4e8ee4a1c89811d0aad7cdc645b00b11ea75d/src/Sentry/Envelopes/Envelope.cs#L187 I'd suggest...

depends on https://github.com/getsentry/sentry-dotnet/issues/1469

We could somehow expose a workaround for now - call the following after ClearAttachments(): ```c# SentrySdk.ConfigureScope(s => s.AddAttachment(new ScreenshotAttachment( new ScreenshotAttachmentContent(options, SentryMonoBehaviour.Instance)))); ``` but those are currently `internal`

I already mentioned this as a TODO in the other IL2CPP line number support issue: #895 - I thought we could just reuse SmokeTester.cs? Or are the line numbers only...

I'm having trouble running this on iOS (on Unity 2021) - always getting il2cppmethods null (as defined here: https://github.com/getsentry/sentry-unity/blob/27d2de0974115faddcdda7ba7de3aa52224ab579/package-dev/Runtime/SentryInitialization.cs#L109)

TODO * [ ] update integration test (SmokeTester.cs) to check the captured exceptions - they must contain line numbers.