Constant |
Code |
Description |
|---|---|---|
|
|
Error raised with an unknown type |
|
|
Error raised when the track can not be initialized. The cause of
this error is a |
|
|
Error raised when the audio decoder can not be initialized. The cause of
this error is a |
|
|
Raised when an error occurs while writing to the audio track. The cause of
this error is a |
|
|
Raised when an error occurs while decrypting audio data. The cause of
this error is a |
|
|
Raised when the video decoder can not be initialized. The cause of
this error is a |
|
|
Raised when an error occurs while decrypting audio data. The cause of
this error is a |
|
|
This error type is raised when loading the player manifest (i.e. the DASH mpd, or
the HLS playlist) failed. The cause of this error is an |
|
|
Error raised when the SDK could not be initialised successfully. The cause of the error is
a |
|
|
Error raised when no plugin was found that can be used to create a renderer to playback a
given DRM and content combination. An error of this type will be raised for example
if you are trying to playback a DASH stream using OMA-DRM but the OMA-Plugin was not loaded.
It is possible also that this Exception is thrown if a Renderer has been temporarily
disabled. A few use cases, such as performing background playback ,can disable a
number of Renderers.
This error has no cause attached to it.
This is reported as |
|
|
Error raised when the applied filters were not able to find any viable content that can
be displayed on the current device. This can happen for example when you are trying to
playback 4K video on a device that does not support it and 4K is the only representation
found in the Manifest.
This is reported as |
|
|
Error raised when the ExoPlayer reports a general playback error. The cause of this
error is a |
|
|
This error is raised if a method is called that is not supported on the current API level.
This will for example be triggered if you try to use Widevine DRM on devices that do not
support it.
This is reported as |
|
|
This error is raised if you are trying to use a DRM system that is not supported by the
device. The cause if this error is a |
|
|
Error raised when the SDK was not initialized using one of |
|
|
This error is raised if an exception occurred while the player was communicating with
DRMToday to fetch a license. The cause of this error is a
|
|
|
This error is raised if an exception occurred while downloading playback data. The cause
of this error is a |
|
|
This error is raised if a secondary display is detected and the current configuration
does not permit playback on that display.
This is reported as |
|
|
This error is raised if a DRM key expires during playback.
This is reported as |
|
|
This error is raised if a DRM key could not be fetched successfully. This is usually caused
when offline lincenses are loaded.
This is reported as |
|
|
This error is raised if an exception occurred while downloading playback and no network
connectivity is available.
This is reported as |
|
|
This exception is raised after the player lost connectivity ( |
|
|
Error raised when the current playback position is behind the live edge in a live stream.
The cause of this error is a |
|
|
Error raised when the Castlabs player license is invalid or expired. Please contact
support if you see this error unexpectedly. Note that if this error occurs, playback is
prevented and the player will stop working.
This is reported as |
|
|
This error is raised if an exception occurred while downloading data. The cause
can be used to identify the root cause. In contrast to |
|
|
This error is raised if an exception occurred while the player was communicating with
DRM server to fetch a license. The cause of this error is a
|
|
|
This error is raised if all audio tracks are filtered out as unsupported.
It is reported as |
|
|
This error is raised if all video tracks are filtered out as unsupported.
It is reported as |
|
|
This error is raised if all text tracks are filtered out as unsupported.
It is reported as |
|
|
Error raised when the userID is mandatory and has not been provided.
This is reported as |
|
|
This error type is raised when parsing the player manifest (i.e. the DASH mpd, or
the HLS playlist) failed. The cause of this error is an |
|
|
Error raised when trying to play Ads but the current Player setup doesn’t support it.
This is the case when using a |
|
|
Error raised during device provisioning
This is reported as |
|
|
Error raised when concurrent stream limiting reaches maximum clients
This is reported as |
|
|
Error raised when there’s a network error with the concurrent stream limiting service
This is reported as |
|
|
This exception is raised after the player sees changes in HDCP connectivity.
This is reported as |
|
|
This error is raised when a general error occurs at initializing or during an Ad. |
|
|
This error is raised when a DNS server error occurs. |
|
|
This error is raised when a timeout error occurs. |
|
|
This error happens when the player found a semantic issue with a Manifest. This could be due to a change in between manifest updates deemed as illegal by the corresponding spec. |
|
|
This error happens when tunneling mode can not be enabled on a device and the playback in
non-tunneling mode continues.
It is reported as |
|
|
This error is raised when video quality blocklisting fails as the current quality is the only
video quality left for playback.
It is reported as |