"Tears of Steel (PlayReady)" is not working on Tizen 3.

[avelad]

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

What version of Shaka Player are you using?: 2.5.0-beta2

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?: Both

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

What browser and OS are you using?:
Tizen 3

What are the manifest and license server URIs?:
{
name: 'Tears of Steel (PlayReady)',
manifestUri: 'https://demo.unified-streaming.com/video/tears-of-steel/tears-of-steel-dash-playready.ism/.mpd',

encoder: shakaAssets.Encoder.UNIFIED_STREAMING,
source: shakaAssets.Source.UNIFIED_STREAMING,
drm: [
  shakaAssets.KeySystem.PLAYREADY,
],
features: [
  shakaAssets.Feature.DASH,
  shakaAssets.Feature.EMBEDDED_TEXT,
  shakaAssets.Feature.HIGH_DEFINITION,
  shakaAssets.Feature.MP4,
  shakaAssets.Feature.SEGMENT_TEMPLATE_TIMELINE,
  shakaAssets.Feature.SUBTITLES,
  shakaAssets.Feature.TTML,
  shakaAssets.Feature.ULTRA_HIGH_DEFINITION,
],

licenseServers: {
  'com.microsoft.playready': 'https://test.playready.microsoft.com/service/rightsmanager.asmx?PlayRight=1&UseSimpleNonPersistentLicense=1',
},

}

What did you do?
Load the stream

What did you expect to happen?
The stream works without problem.

What actually happened?
I see ShakaPlayer error 4012 with a message "missing keys". The same stream works on Edge.

[TheModMaker]

Both Edge and Chromecast's implementations of PlayReady use an incorrect byte-ordering in the key IDs, see this workaround. But it seems like Tizen doesn't do this.

[joeyparrish]

Fix cherry-picked for v2.4.6.