RUM-1871 Reduced view update may miss hasReplay flag set before

[barboraplasovska]

What and why?

RUM backend has a special handling for hasReplay flag - once it is sent to true in any view update it cannot go back to false.

On the client side, however, we reduce the views, keeping only the last view update for a given viewId in the batch. If this view had originally hasReplay: true and then last view update has hasReplay:false (because by the time view update is sent session replay is disabled) we will miss session replay info for this view.

How?

Introduction of a new private attribute hasReplay in the RUMViewScope class that is set each time a new View event is built. In the case that it has once been set to true, each following RUMViewEvent that is created will keep hasReplay set to true.

Review checklist

• Feature or bugfix MUST have appropriate tests (unit, integration)
• Make sure each commit and the PR mention the Issue number or JIRA reference
• Add CHANGELOG entry for user facing changes
• Add Objective-C interface for public APIs (see our guidelines [internal]) and run make api-surface)

[datadog-datadog-prod-us1]

Datadog Report

Branch report: bplasovska/RUM-1871/hasReplay-update
Commit report: b787f69
Test service: dd-sdk-ios

✅ 0 Failed, 782 Passed, 3030 Skipped, 1m 6.49s Total duration (1m 26.48s time saved)

[maxep]

To the point, very nice work 🎖️ 👍

[mariedm]

Looks great, nice job! 👏