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

WebOS 3.5 is throwing "Failed to execute 'webkitGenerateKeyRequest' on 'HTMLMediaElement': The key system provided ('com.microsoft.playready') is not supported" error. #7770

Open
subhanahmed047 opened this issue Dec 17, 2024 · 13 comments · Fixed by #8083
Assignees
Labels
component: PlayReady The issue involves the PlayReady DRM platform: WebOS Issues affecting WebOS priority: P1 Big impact or workaround impractical; resolve before feature release type: bug Something isn't working correctly
Milestone

Comments

@subhanahmed047
Copy link
Contributor

Have you read the FAQ and checked for duplicate open issues?
Yes

If the problem is related to FairPlay, have you read the tutorial?

No

What version of Shaka Player are you using?

4.12.4

Can you reproduce the issue with our latest release version?
Yes

Can you reproduce the issue with the latest code from main?
Yes

Are you using the demo app or your own custom app?
Demo App

If custom app, can you reproduce the issue using our demo app?
Yes

What browser and OS are you using?
Chrome 38 on WebOS 3.5 (LG 2017)

For embedded devices (smart TVs, etc.), what model and firmware version are you using?
Software Version: 05.70.35

What are the manifest and license server URIs?

I'm using the Axinom test vectors. You can find the demo as well the URLs here -> https://github.com/subhanahmed047/shaka-player-demo/blob/main/index.js#L1-L8

What configuration are you using? What is the output of player.getNonDefaultConfiguration()?

 player.configure({
        drm: {
            servers: {
                [keySystem]: licenseServerUrl,
            },
        },
        preferredVideoCodecs: ['avc1.640028'],
    })

What did you do?

Simply run the above-mentioned demo.

What did you expect to happen?
I expected to see the playback. The current version I'm running with working playback is v4.7.11.

What actually happened?

I get the following error:

Failed to execute 'webkitGenerateKeyRequest' on 'HTMLMediaElement': The key system provided ('com.microsoft.playready') is not supported.

Screenshot 2024-12-17 at 2 29 11 pm

This exact error has been fixed in the past here -> #6558

However back then the issue would come up as a 4032 error instead of the 6006 error.

Are you planning to send a PR to fix it?
Maybe, I just wanted to raise this issue to see if I can get some pointers.

@subhanahmed047 subhanahmed047 added the type: bug Something isn't working correctly label Dec 17, 2024
@shaka-bot shaka-bot added this to the v4.13 milestone Dec 17, 2024
@tykus160
Copy link
Member

@subhanahmed047 tbh it looks like PlayReady is not supported anymore on WebOS, but that would be very surprising. Can you show us a result of shaka.Player.probeSupport()? You can also try to run https://shaka-player-demo.appspot.com/support.html on a TV.

@tykus160 tykus160 added component: PlayReady The issue involves the PlayReady DRM platform: WebOS Issues affecting WebOS status: waiting on response Waiting on a response from the reporter(s) of the issue labels Dec 18, 2024
@avelad
Copy link
Member

avelad commented Dec 20, 2024

@subhanahmed047 tbh it looks like PlayReady is not supported anymore on WebOS, but that would be very surprising. Can you show us a result of shaka.Player.probeSupport()? You can also try to run https://shaka-player-demo.appspot.com/support.html on a TV.

Where have you seen that it is not supported? According to the webos developers it is supported... https://webostv.developer.lge.com/develop/specifications/streaming-protocol-drm

@tykus160
Copy link
Member

@avelad I meant this particular device claims it's not supported, I haven't seen any indication of that on LG documentation. We need to find out is it really not supported sometimes or do we have some issue in our polyfill.

@shaka-bot
Copy link
Collaborator

Closing due to inactivity. If this is still an issue for you or if you have further questions, the OP can ask shaka-bot to reopen it by including @shaka-bot reopen in a comment.

@shaka-bot shaka-bot removed the status: waiting on response Waiting on a response from the reporter(s) of the issue label Dec 26, 2024
@tykus160 tykus160 reopened this Feb 4, 2025
@tykus160 tykus160 self-assigned this Feb 4, 2025
@tykus160
Copy link
Member

tykus160 commented Feb 4, 2025

This is another occurrence of #2915 probably caused by introducing Preload Manager

@avelad avelad modified the milestones: v4.13, v4.14 Feb 4, 2025
@koenoe
Copy link
Contributor

koenoe commented Feb 5, 2025

I can reproduce this on WebOS 3.0 with both Widevine and Playready. I tried debugging it, but looks like there's some EME polyfill missing, but couldn't figure out where exactly. Sorry if this isn't too helpful 😅

@avelad avelad added the priority: P1 Big impact or workaround impractical; resolve before feature release label Feb 17, 2025
tykus160 added a commit that referenced this issue Feb 17, 2025
Fixes #7770 
Webkit DRM heavily relies on video element, so it needs to be provided
in proper order to avoid any issues.

---------

Co-authored-by: Álvaro Velad Galván <[email protected]>
tykus160 added a commit that referenced this issue Feb 17, 2025
Fixes #7770 
Webkit DRM heavily relies on video element, so it needs to be provided
in proper order to avoid any issues.

---------

Co-authored-by: Álvaro Velad Galván <[email protected]>
tykus160 added a commit that referenced this issue Feb 17, 2025
Fixes #7770 
Webkit DRM heavily relies on video element, so it needs to be provided
in proper order to avoid any issues.

---------

Co-authored-by: Álvaro Velad Galván <[email protected]>
@subhanahmed047
Copy link
Contributor Author

@tykus160 @avelad Apologies for the late response, I was off sick. I just tried running Shaka Player v4.13.4 on webos3 and got the same error as I reported above.

@tykus160 tykus160 reopened this Feb 25, 2025
@tykus160
Copy link
Member

@subhanahmed047 sad to hear that, as this fix is working for us internally.
Are you able to share verbose logs with us (call shaka.log.setLevel(shaka.log.Level.V2))?

@subhanahmed047
Copy link
Contributor Author

subhanahmed047 commented Feb 26, 2025

@tykus160 I just tried the following Widevine-protected HLS stream from Shaka's demo page:
https://storage.googleapis.com/shaka-demo-assets/angel-one-widevine-hls/hls.m3u8
https://cwip-shaka-proxy.appspot.com/no_auth

> shaka.Player.version
v4.13.4-debug

Here are the results (Please ignore my custom logs).
Image

Image

@tykus160
Copy link
Member

@subhanahmed047 do you see it only on Widevine now, or on PlayReady as well?

@subhanahmed047
Copy link
Contributor Author

It's both. I just chose Widevine for the above test. I did try playready too.

@tykus160
Copy link
Member

Are you able to look into this? I'm afraid I'm not able to reproduce it now. Probably you'd need to dive into logic I changed before and check what can be adjusted.

@subhanahmed047
Copy link
Contributor Author

No worries, I'll look at it next week when I'm in front of a WebOS3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: PlayReady The issue involves the PlayReady DRM platform: WebOS Issues affecting WebOS priority: P1 Big impact or workaround impractical; resolve before feature release type: bug Something isn't working correctly
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants
@koenoe @subhanahmed047 @avelad @shaka-bot @tykus160 and others