Missing decryption key after succesful license request when using persistentStateRequired

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

What version of Shaka Player are you using?: 2.4.3

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

Can you reproduce the issue with the latest code from master?: Yes

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

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

What browser and OS are you using?: Firefox 61.0.2 and Chrome 68.0.3440.106 on Mac OS High Sierra

What are the manifest and license server URIs?: Not able to share at the moment since I don’t own the rights to the affected assets. I will try to find a test asset that reproduces the issue.

What did you do? Play a Widevine DRM protected video multiple times. Set the persistentStateRequired option to true in order to allow device registration.

What did you expect to happen? Playback to succeed every time

What actually happened? Playback fails randomly, about 1 out of 40 times (i.e. if you refresh the page multiple times). When playback fails, the license request returns with a 200 status, but the browser fails to decrypt segments with the newly acquired key.

On Chrome you can see the following in chrome://media-internals/ :

Note the “no key for key ID” entry that is shown after “key added, resuming decode”

On Firefox, segment decoding fails:

I realize that this is most likely a Widevine, rather than a Shaka issue, but there’s no other Widevine-related forum that I have access to. I’m hoping someone can point me to documentation about a known-issue or perhaps suggest a workaround. Thanks

[dzianis-dashkevich-old]

hello, have you received any updates on this issue?

[TheModMaker]

From the Chrome issue:

We missed the M71 branch cut to land the CDM with this change. This change will be in M72 Chrome.

I don’t have a specific CDM version where the fix appears.

Would it also be necessary to open a ticket with Firefox about this, or do they pick up CDM updates regularly? Thanks

I am not familiar with Firefox’s CDM updates. It was entirely a fix in the CDM, so Firefox only needs to update to get it. But you should talk with them to determine when the fix will appear.