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

feat: use engage-sdk for continue watching #150

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

vighnesh153
Copy link
Contributor

This Pull request integrates Engage SDK with TV samples app. In the current implementation, we are making use of androidx.tvprovider to update the Watch Next program row on a TV device. Since androidx.tvprovider is no longer maintained and we are now moving towards cross-device continue watching, we are migrating to making use of Engage SDK to publish to the watch next program row on a TV device.

@jpgpuyo
Copy link

jpgpuyo commented Feb 3, 2024

Hello @vighnesh153,
Thanks a lot for your effort.
I have tried reference app in Chromecast HD with Google TV and Play Next row is not working any more. I suspect that the issue is that in Google TV we have 'Continue watching' row instead of 'Play Next'.

Once this new SDK is integrated, can you clarify which is the compatibility with older TVs with 'Play next' row?

Thanks!

@vighnesh153
Copy link
Contributor Author

2 reasons why the integration isn't working:

  1. Engage SDK 1.4.0 version is not yet published engage-sdk-maven-repo
  2. Engage Service has an allowlisting mechanism at the backend to allow only certain apps to publish to tv provider. Currently, this Reference app is not yet allowlisted for publishing to TV provider.

@chikoski
Copy link
Contributor

chikoski commented Mar 6, 2024

I will review this PR, but I am not familiar with the API.

@miguelmontemayor Would you please review this PR if it uses API properly or not?

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.

None yet

4 participants