DRM error codes
SSP errors
The following errors can occur while trying to play encrypted content.
| What | Extra | Description | Application error handling recommendation |
|---|---|---|---|
| MEDIA_ERROR_SSP = -3100 | Error code returned from SSP server, see:
For more information see Content License Mgt Service (CLM). | ||
| MEDIA_ERROR_PROVISION = -3200 | 0 | The device is not provisioned. | |
| MEDIA_ERROR_OPY_DRM_DECRYPTION_FAILURE = -1355 | ERROR_NO_KEY = 1 | The KEY to decrypt the stream is not found. | |
| ERROR_KEY_EXPIRED = 2 | The KEY used to decrypt the stream is not valid due to licence expiry. | ||
| ERROR_RESOURCE_BUSY = 3 | The required crypto resource is not available. | ||
| ERROR_INSUFFICIENT_OUTPUT_PROTECTION = 4 | The device output protection policy is not sufficient. | ||
| ERROR_SESSION_NOT_OPENED = 5 | Decryption attempted on a session that is not opened or closed prematurely. | ||
| ERROR_UNSUPPORTED_OPERATION = 6 | The attempted operation could not be supported. | ||
| ERROR_INSUFFICIENT_SECURITY = 7 | The security level of the device is not sufficient. | ||
| ERROR_FRAME_TOO_LARGE = 8 | The decrypted video frame exceeds the size of device output buffers. | ||
| ERROR_LOST_STATE = 9 | The DRM session state is invalidated. | ||
| MEDIA_ERROR_OPY_DRM_NOT_SUPPORTED = -1356 | 0 | The DRM type not supported by the device. | |
| MEDIA_ERROR_DECODER_ERROR = -1357 | 0 | MEDIA_ERROR_DECODER_ERROR is a general error; all related decoder errors will cause the player SDK to throw this error. E.g. failure to initialize decoder, failure to query decoder, failure to decode media sample, or trying to decode but the format is not supported or exceeds the capabilities of the device. | |
| MEDIA_ERROR_LICENSE_KEY_EXPIRED = -1358 | 0 | The licence key expired. | Can retry playback to fetch a new licence for Live stream for App to have a smooth user experience. |
| MEDIA_ERROR_LICENSE_SESSION_FAILURE = -1359 | 0 | Failure of DRM operation on current DRMSession, e.g. store the key, release key. | No retry |
| MEDIA_ERROR_LICENSE_SCHEME_DATA_FAILURE = -1360 | 0 | drmInitData is missing for DRM UUID. | No retry |
| MEDIA_ERROR_LICENSE_DRM_SESSION_FAILURE = -1361 | 0 | Licence fetch failure for encrypted stream. | No retry, unless App is certain invalid token App causes the failure, can re-try playback with a new valid token. |
PAK DRM Errors
The following errors can occur while trying to play PRM encrypted content. The application should ignore the error handling for this category if PRM is not enabled in the platform.
| What | Extra | Description | Application error handle recommendation |
|---|---|---|---|
| MEDIA_ERROR_PAK = -2000 | MEDIA_ERROR_PAK_UNKNOWN = -2001 | Other PAK-specific error. | |
| MEDIA_ERROR_PAK_LICENSE_FETCH_FAILURE = -2002 | PAK DRM-specific licence fetch failure for encrypted stream. | No retry | |
| MEDIA_ERROR_PAK_ACCESS_DENIED = -2003 | PAK DRM-specific licence fetch success but the licence does not contain the right key. | No retry |
CONNECT DRM errors
The following errors can occur while trying to play CONNECT encrypted content.
| What | Extra | Description | Application error handling recommendation |
|---|---|---|---|
| MEDIA_ERROR_CONNECT =-3000 | MEDIA_ERROR_CONNECT_UNKNOWN = -3001 | Other CONNECT DRM-specific failure, e.g. the hardware resource not available. | |
| MEDIA_ERROR_CONNECT_LICENSE_FETCH_FAILURE = -3002 | CONNECT DRM-specific licence fetch failure for encrypted stream. | ||
| MEDIA_ERROR_CONNECT_KEY_STATUS_INVALID = -3003 | CONNECT DRM-specific licence fetch success, but the key is not usable for encrypted stream. | ||
| MEDIA_ERROR_CONNECT_NOT_PROVISIONED = -3004 | CONNECT DRM is being used while not provisioned yet. | ||
| MEDIA_ERROR_CONNECT_DECRYPTION_FAILURE = -3006 | CONNECT DRM run-time decryption failure. |