You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Per #5376: the SDK has drifted into keeping the Scope largely unpopulated and relying on the Enricher to lazily backfill values like Environment/Release, plus a second pipeline (SetDefaultAttributes) living outside both mechanisms... meaning a user-set Environment on the scope could simply be ignored.
At Init:SentryOptions.Environment isn't being pushed into the native SDK, so events originating natively (e.g. a native crash) could carry the wrong/default environment while managed events carried the user's value — inconsistent tagging on the same app.
After Init: The scope lets a user overwrite Environment at runtime, but that change isn't propagated.
Note
This issue relates to sentry-native and sentry-cocoa only. sentry-java is addressed separately via:
Tracking issue for :
environmentto the native layers #5365Scopefirst #5376Problem
Per #5376: the SDK has drifted into keeping the
Scopelargely unpopulated and relying on theEnricherto lazily backfill values likeEnvironment/Release, plus a second pipeline (SetDefaultAttributes) living outside both mechanisms... meaning a user-setEnvironmenton the scope could simply be ignored.SentryOptions.Environmentisn't being pushed into the native SDK, so events originating natively (e.g. a native crash) could carry the wrong/default environment while managed events carried the user's value — inconsistent tagging on the same app.Environmentat runtime, but that change isn't propagated.Note
This issue relates to
sentry-nativeandsentry-cocoaonly.sentry-javais addressed separately via:EnvironmentviaIScopeObserverin Hybrid SDK scenarios (sentry-java) #5387