Sentry Unity SDK (3.2.4) Random SIGILL on Android + Wrong Environment Name (“production”)

[altkey-KevinLachance]

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

We receiving random SIGILL (Illegal Instruction) events on Android devices during Sentry initialization.

The crash does not originate from our code, and it happens before our SetBeforeSend filter runs.
Additionally, the event is tagged with environment = "production" even though our project never assigns "production" anywhere, indicating that Sentry is applying its own environment before our configuration executes.

This suggests a crash occurring inside the native layer during SDK initialization, before our BeforeSend callback is allowed to cancel events.

I can send you more info via e-mail (bug link and dsn)

Unity | 6000.2.13
Sentry Unity SDK | 3.2.4 (io.sentry.unity from GitHub)
Android | 11
Devices Affected | OnePlus 8 Pro (and others)
Architecture | ARM64
IL2CPP | Yes
Install Mode | Google Play Store

Expected Result

no fatal crash

Actual Result

fatal crash

Product Area

Unknown

Link

No response

DSN

No response

Version

No response

[linear]

ENG-6028

UNITY-189

UNITY-190

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[bitsandfoxes]

@altkey-KevinLachance, thanks for reaching out. The environment production is the default value, indicating, as you said, that the SDK is crashing during initialization, before your code is even reached. If you could send any further information to stefan@sentry.io, I'd highly appreciate it.