[Android][Chrome][Widevine][Dash] Error 6002 FAILED_TO_CREATE_CDM

[CHaNGeTe]

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

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

What version of Shaka Player are you using? 4.12.4 / 4.12.5

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

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

What browser and OS are you using?
Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Mobile Safari/537.36
Android Chrome 131.0.6778.105 on Android 14

For embedded devices (smart TVs, etc.), what model and firmware version are you using? N/A

What are the manifest and license server URIs? Email

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

{
  "drm": {
    "servers": {
      "com.widevine.alpha": "SENT ON EMAIL"
    }
  },
  "manifest": {
    "hls": {
      "ignoreTextStreamFailures": true
    }
  },
  "streaming": {
    "ignoreTextStreamFailures": true,
    "alwaysStreamText": true
  }
}

What did you do?
Play Widevine Dash asset on Android Chrome

What did you expect to happen?
To always play

What actually happened?

Sometimes it works.
But sometimes (most of times) I receive 6002 FAILED_TO_CREATE_CDM / Unable to create MediaCrypto session

I have the feeling the queryMediaKeys promises are not correctly resolving.

Are you planning send a PR to fix it?
I tried debugging it, but not for now

[CHaNGeTe]

For some reason the asset works fine on Mac Chrome but I am having issues on Android Chrome

[CHaNGeTe]

I noticed this:
Reattempting the mediaKeySystemAccess.createMediaKeys() call after some time can lead to success getting the mediaKeys.

The rate of successful playback attempts has increased a lot by the reattempt

[CHaNGeTe]

I have observed that this log is shown when it works vs not when it doesn't:
https://github.com/24i/shaka-player-probeSupport/blob/60429e93f9bd90a2f3448dd22958e6f70ab8028d/lib/util/stream_utils.js#L750-L753

[CHaNGeTe]

I have increased the % but it is still not bulletproof:

Attempt 1 to create MediaKeys
shaka-player.compiled.debug.js:144 Failed to create MediaKeys on attempt 1 null MediaKeySystemAccess {keySystem: 'com.widevine.alpha'} NotSupportedError: Unable to create MediaCrypto session.
shaka-player.compiled.debug.js:144 Attempt 2 to create MediaKeys
shaka-player.compiled.debug.js:144 Failed to create MediaKeys on attempt 2 null MediaKeySystemAccess {keySystem: 'com.widevine.alpha'} NotSupportedError: Unable to create MediaCrypto session.
shaka-player.compiled.debug.js:144 All attempts to create MediaKeys failed
shaka-player.compiled.debug.js:144 Attempt 1 to create MediaKeys
shaka-player.compiled.debug.js:144 Failed to create MediaKeys on attempt 1 null MediaKeySystemAccess {keySystem: 'com.widevine.alpha'} NotSupportedError: Unable to create MediaCrypto session.
shaka-player.compiled.debug.js:144 Attempt 2 to create MediaKeys
shaka-player.compiled.debug.js:144 Failed to create MediaKeys on attempt 2 null MediaKeySystemAccess {keySystem: 'com.widevine.alpha'} NotSupportedError: Unable to create MediaCrypto session.
shaka-player.compiled.debug.js:144 All attempts to create MediaKeys failed
shaka-player.compiled.debug.js:144 Attempt 1 to create MediaKeys
shaka-player.compiled.debug.js:144 Succeeded to create MediaKeys on attempt 1 null

Seems Widevine CDM is not fully ready when it happens, but at least I am not aware of any method to check its readyness

[CHaNGeTe]

BTW seems Widevine CDM readyness is very tied to the specified robutsness
SW_* robustness makes createMediakeys work on first attempt for now on 100% of my tries:

advanced: {
      'com.widevine.alpha': {
          'videoRobustness': 'SW_SECURE_DECODE',
          'audioRobustness': 'SW_SECURE_CRYPTO'
      }
  },

The issues is noticeable when no robustness is specified on Android Chrome

[CHaNGeTe]

Well seems it is more SW/HW vs '' (empty) robustness
So seems at least on Android Chrome has come the day this is actually true:

[CHaNGeTe]

Thanks @avelad