RUM-16682: Add crash count 0 to RUM view event#183
Merged
Conversation
kikoveiga
approved these changes
Jun 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
This PR adds missing attribute
crash.countinto RUM view event, without this attribute the backend will not take this view into account the metric ofrum.measure.view.crash_free.Why
crash.count0 here? Roku doesn't have the in-process crash as JVM crash in Android SDK, Roku SDK always retrieves the crash information from a new session and reportscrash.count1 inRumCrashReporterTaskMotivation
RUM-16682
Review checklist (to be filled by reviewers)