The SDK encountered a severe error (for example, invalid license or API call failure) that makes it impossible for stream publishing to continue.
Video encoding failure does not affect publishing. The SDK will handle the issue automatically to ensure successful encoding of subsequent frames.
|A common error not yet classified
|An invalid parameter was passed to the API.
|The API call was rejected.
|The API cannot be called.
|Failed to call the API because the license is invalid. Note: Before calling
startLivePlay, you need to call
V2TXLivePremier#setLicence to configure the license (you only need to configure the license once). Otherwise, playback will fail (black screen). You can use a live stream publishing license, UGSV license, or video playback license to activate the playback feature. If you don’t have any of the licenses, you can buy one or apply for a trial license for free.
|The request timed out.
|The server denied the request.
|The SDK was disconnected.
|Could not find an available HEVC decoder. This error code indicates that the current device does not support H.265 decoding. Please switch to H.264 for playback.
Most warning events trigger protection or recovery logic that involves retries. In most cases, the problems can be fixed by the SDK itself. However, some warning events still need to be handled manually. Warnings serve the purpose of reminding you or your end users that an error occurred.
|Bad network connection: Data upload blocked due to limited upstream bandwidth.
|Stuttering during video playback.
|Failed to turn the camera on.
|The camera is occupied. Try a different camera.
|No access to the camera. This usually occurs on mobile devices and may be because the user denied the access.
|Failed to turn the mic on.
|The mic is occupied. This occurs when, for example, the user is having a call on the mobile device.
|No access to the mic. This usually occurs on mobile devices and may be because the user denied the access.
|The system does not support screen sharing.
|Failed to start screen recording. If this occurs on a mobile device, it may be because the user denied the access.
|Screen recording was stopped by the system.