Description
We've documented here: https://docs.sentry.io/platforms/unity/configuration/releases/
The Crash Free Session Rate requires native support. On platforms that don't yet have native support, the SDK reports sessions that did not end gracefully as Abnormal, which leads to 100% crash free sessions being recorded. If you're building on a platform that doesn't have native support yet, you should monitor your app's Abnormal rate.
This could potentially be improved in the product to surface a distinction when "crash" isn't possible. Either by focusing on 'abnormal' or another strategy. Additionally we could document or automate a way to have a distinction in the "release name" for builds that support "crash free rate" vs those that only report healthy/abnormal.
Related to:
Metadata
Metadata
Assignees
Type
Projects
Status
Status