captureException() with level 'warning' marks sessions as errored on Android but not iOS

[quintasda]

SDK: @sentry/react-native@6.17.0

When using Sentry.captureException() with level: 'warning' in React Native, iOS and Android native SDKs handle session health marking inconsistently:

• iOS: Does NOT mark session as errored - appears to filter by severity level
• Android: DOES mark session as errored - marks all captureException() calls regardless of level

After switching from level: 'error' to level: 'warning':

iOS release data:
├─ Crash Free Rate: 99.996% (↑ 0.003%)
├─ Healthy: 93.346% (↑ 28.383%) ✅
├─ Errored: 4.174% (↓ 29.842%) ✅
└─ Abnormal: 2.476% (↑ 1.462%)

Android Release data:
├─ Crash Free Rate: 99.992% (↓ 0.002%)
├─ Healthy: 47.836% (↓ 16.055%) ❌
├─ Errored: 52.156% (↑ 16.896%) ❌
└─ Abnormal: 0% (↓ 0.843%)

[linear]

NATIVE-134

[linear]

RN-358

[antonis]

Noting that the level is not mentioned as a factor in how sessions are classified as healthy, errored, or crashed in the official documentation Release Health Session Status. Along with resolving this issue we should update the related docs.

https://develop.sentry.dev/sdk/telemetry/sessions/#crashed-abnormal-vs-errored