Propagate feature flags to fatal error RUM events#2688
Conversation
|
/merge |
|
View all feedbacks in Devflow UI.
This pull request is not mergeable according to GitHub. Common reasons include pending required checks, missing approvals, or merge conflicts — but it could also be blocked by other repository rules or settings.
devflow unqueued this merge request: It did not become mergeable within the expected time |
4e48766 to
e900e03
Compare
FatalErrorBuilder omitted featureFlags when constructing RUM error and view events for crashes, fatal app hangs, and watchdog terminations. This caused feature flags present on the last RUM view to be lost in the resulting error/view events sent to the backend. Co-Authored-By: Claude Opus 4.6 <[email protected]>
e900e03 to
9cdcaf5
Compare
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
|
Summary
featureFlagspropagation inFatalErrorBuilderwhen constructing RUM error and view events for crashes, fatal app hangs, and watchdog terminationsCrashReportReceiverTestsChanges
FatalErrorBuilder.createRUMError(): passfeatureFlagsfrom the lastRUMViewEventto theRUMErrorEventFatalErrorBuilder.updateRUMViewWithError(): preservefeatureFlagsfrom the originalRUMViewEventRUMDataModelMocks: threadfeatureFlagsparameter throughmockRandomWith()CHANGELOG.md: add[FIX]entry under UnreleasedTest plan
testGivenCrashDuringRUMSessionWithActiveViewAndFeatureFlags_itSendsEventsWithFeatureFlagsverifies both error and view events propagate feature flagsCrashReportReceiverTestspass (no regressions)🤖 Generated with Claude Code