Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Flag-to-track-video-resume-as-CONTENT-START #69

Conversation

sathya-sundar
Copy link

@sathya-sundar sathya-sundar commented May 30, 2024

Issue Description:
Our App has a feature to let user play content from a resume position. We noticed below issue in New Relic reporting when playback initiated using Resume button.

Given: User initiated payback using Resume CTA.

When: videoNode sent to New Relic has videoNode.position > 0

Then: CONTENT_START action not triggered.

Then: Our reports would miss all playbacks initiated through Resume CTA.

Fix:
To fix the above issue, i have added a flag called m.nrShouldTrackResumeAsContentStart, which can be set by the App.
If this flag is set to true, app will trigger CONTENT_START action even if videoNode.position > 0. If will only check if the state changed to playing after initial buffer to trigger the CONTENT_START action.

@CLAassistant
Copy link

CLAassistant commented May 30, 2024

CLA assistant check
All committers have signed the CLA.

@@ -1427,7 +1438,7 @@ function nrStateTransitionPlaying() as Void
shouldSendStart = m.nrIsInitialBuffering
nrSendBufferEnd()

if m.nrVideoObject.position = 0
if m.nrVideoObject.position = 0 or m.nrShouldTrackResumeAsContentStart
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion for New Relic folks:
It might be cleaner to remove the position = 0 check. I don't see this check being performed in newrelic-video-core.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@sathya-sundar have you tried @timalacey's solution? That should fix the issue without the need of introducing the nrShouldTrackResumeAsContentStart flag.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@sathya-sundar this PR should fix your issue. Could you test it and confirm?

@asllop
Copy link
Contributor

asllop commented Jul 22, 2024

We just release a new version (3.2.5) that should fix this issue.

@asllop asllop closed this Jul 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants