Skip to content

fix: Bail out on other decodingInfos when we found a preferred and supported one. #8829

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

Merged
merged 2 commits into from
Jul 2, 2025

Conversation

matvp91
Copy link
Member

@matvp91 matvp91 commented Jul 2, 2025

Pick a multi DRM asset, set preferredKeySystems to prefer PlayReady over Widevine and run on a device that does not support PlayReady (eg; Chrome).

A REQUESTED_KEY_SYSTEM_CONFIG_UNAVAILABLE is thrown.

This is due to the logic in getDecodingInfosForVariants where we bail out on probing other decodingInfos when we found a prefered one, but we didn't check whether it was supported or not. As a result, Widevine was never checked and PlayReady was left marked as unsupported.

@matvp91 matvp91 changed the title feat: Bail out on other decodingInfos when we found a preferred and supported one. fix: Bail out on other decodingInfos when we found a preferred and supported one. Jul 2, 2025
@avelad avelad added type: bug Something isn't working correctly priority: P1 Big impact or workaround impractical; resolve before feature release labels Jul 2, 2025
@avelad avelad added this to the v4.16 milestone Jul 2, 2025
@avelad avelad requested review from avelad and tykus160 July 2, 2025 09:21
@shaka-bot
Copy link
Collaborator

Incremental code coverage: 100.00%

@avelad avelad merged commit 5245bc3 into shaka-project:main Jul 2, 2025
31 of 32 checks passed
avelad pushed a commit that referenced this pull request Jul 7, 2025
…pported one. (#8829)

Pick a multi DRM asset, set `preferredKeySystems` to prefer PlayReady
over Widevine and run on a device that does not support PlayReady (eg;
Chrome).

A `REQUESTED_KEY_SYSTEM_CONFIG_UNAVAILABLE` is thrown.

This is due to the logic in `getDecodingInfosForVariants` where we bail
out on probing other decodingInfos when we found a prefered one, but we
didn't check whether it was supported or not. As a result, Widevine was
never checked and PlayReady was left marked as unsupported.
avelad pushed a commit that referenced this pull request Jul 7, 2025
…pported one. (#8829)

Pick a multi DRM asset, set `preferredKeySystems` to prefer PlayReady
over Widevine and run on a device that does not support PlayReady (eg;
Chrome).

A `REQUESTED_KEY_SYSTEM_CONFIG_UNAVAILABLE` is thrown.

This is due to the logic in `getDecodingInfosForVariants` where we bail
out on probing other decodingInfos when we found a prefered one, but we
didn't check whether it was supported or not. As a result, Widevine was
never checked and PlayReady was left marked as unsupported.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: P1 Big impact or workaround impractical; resolve before feature release type: bug Something isn't working correctly
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants