(HLS, TS, AES-128 key rotation) occur 3014, 3016 error in Android Chrome.

[papico-inflab]

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

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

yes

What version of Shaka Player are you using?

v4.7.11

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

What browser and OS are you using?
browser: Chrome (122.0.6261.91)
OS: Android 13

What are the manifest and license server URIs?

https://storage.googleapis.com/shaka-demo-assets/sintel-ts-aes-key-rotation/master.m3u8

Demo site url : https://shaka-player-demo.appspot.com/demo/#audiolang=en-US;textlang=en-US;uilang=en-US;asset=https://storage.googleapis.com/shaka-demo-assets/sintel-ts-aes-key-rotation/master.m3u8;panel=ALL_CONTENT;panelData=drm:AES128,HLS,MP2TS;build=compiled

What did you do?

Enter the link on Android device Chrome

What actually happened?

Error 3016, 3014 when playing with AES-128 key rotation on Android Chrome browser.

[joeyparrish]

Confirmed. It works in ChromeOS and Chrome on Linux, but not Chrome on Android.

We need to check if there is a difference in TS support (is Android transmuxing like Linux and ChromeOS?), and we need to check if webCrypto is operating correctly on Android (unlikely to be the issue, but you never know)

[joeyparrish]

My phone appears to support TS natively, which means we are skipping transmuxing. I didn't realize that was the case.

[avelad]

@joeyparrish I think TS has problems in all browsers, I think we should always do transmuxing in any browser

[joeyparrish]

Agreed. It comes up on TVs, on Android, on Cast... it's a bad format and it's badly-supported. Transmuxing should be better.

[papico-inflab]

@joeyparrish
Any idea when this error might be fixed?
I'm currently playing with rotation aes-128 key encryption and that error is preventing me from updating the version.
Thank you for your attention.

[joeyparrish]

To fix this, we need to force transmuxing on all TS content on all platforms. That will require a new release.

But you can change this behavior with a config today:

// v4.4 through v4.7 (current)
player.configure('mediaSource.forceTransmux', true);

// v4.3
player.configure('streaming.forceTransmux', true);

// v3.0 through v4.2
player.configure('streaming.forceTransmuxTS', true);

Based on this workaround, the priority for the change is set at P2. Apologies for not explaining this workaround explicitly before. @papico-inf, can you please confirm that this workaround works for you?

[framework20]

Same errors - 3014 & 3016 on android (samsung s10+, android 12) with chrome (122.0.6261.105). But error 3014 does not always appear and has data[0]=0. Error 3016 has the following data [3,null, "PIPELINE_ERROR_DECODE"]. Logs from chrome://media-internals attached as a file. Shaka player v4.7.11. Firefox on android and desktop, chrome on desktop works fine. By the way, for some reason chrome on windows 11 and firefox on android allow me to take screenshots.
media-internals.txt

[papico-inflab]

@joeyparrish
I tried setting the options you mentioned, but it doesn't work. 😢

[avelad]

@papico-inf can you test if the https://nightly-dot-shaka-player-demo.appspot.com/ fix the issue? Thanks!

[shaka-bot]

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.